Systems and methods for remote and host monitoring communications

ABSTRACT

Systems and methods for remote and host monitoring communication are disclosed. In some implementations, monitoring systems can comprise a host monitoring device associated with a Host communicatively coupled to one or more remote monitoring devices associated with Remote Monitors. The host monitoring device can send communications based at least in part on analyte measurements of a Host sensor and/or other contextual data giving such measurements context. Different remote monitoring devices can receive different communications based at least in part on the role of the respective Remote Monitors relative to the Host. These roles can be reflected in classifications of Remote Monitors.

CROSS-REFERENCE TO RELATED APPLICATIONS

Any and all priority claims identified in the Application Data Sheet, orany correction thereto, are hereby incorporated by reference under 37C.F.R. § 1.57. This application is a continuation of U.S. applicationSer. No. 15/377,216, filed Dec. 13, 2016, which claims the benefit ofU.S. Provisional Application No. 62/271,840, filed Dec. 28, 2015. Eachof the aforementioned applications is incorporated by reference hereinin its entirety, and each is hereby expressly made a part of thisspecification.

BACKGROUND Field

The present application relates generally to remote monitoring, and morespecifically to systems and methods for remote and host monitoringcommunication.

Description of the Related Art

Analyte monitors can be configured to mount on tissue to detect analytesin a sensing area. For example, analyte monitors can include sensorsthat measure the concentration of glucose, lactate, cholesterol,hemoglobin, and/or other blood or bodily fluid constituents.

In some cases, persons with diabetes mellitus (also known as diabetes)can use an analyte monitor. Diabetes is a disorder in which the pancreasof a person may not create sufficient insulin, such as in the case ofType I diabetes, and/or in which insulin may not be effective for aperson, such as is in the case of Type II diabetes. In a diabetic state,the patient can suffer from high blood sugar, which can cause an arrayof physiological derangements, such as kidney failure, skin ulcers, orbleeding into the vitreous of the eye, which can be associated with thedeterioration of small blood vessels. A hypoglycemic reaction, such aslow blood sugar, can be induced by an inadvertent overdose of insulin,or after a normal dose of insulin or glucose-lowering agent accompaniedby extraordinary exercise or insufficient food intake.

A diabetic can carry an analyte monitor such as a self-monitoring bloodglucose (“SMBG”) monitor, which typically requires uncomfortable fingerpricking methods. Due to the lack of comfort and convenience, a diabetictypically measures his or her glucose level only two to four times perday. Unfortunately, these time intervals can be spread so far apart thatthe diabetic would likely find out too late that he/she has ahyperglycemic or hypoglycemic condition, which can sometimes causedangerous side effects. In fact, it is not only unlikely that a diabeticwould take a timely SMBG value, but additionally, the diabetic wouldlikely not know if his/her blood glucose value is rising or fallingbased on conventional methods.

Consequently, a variety of non-invasive, transdermal (e.g.,transcutaneous) and/or implantable electrochemical sensors have been andare being developed for detecting and/or quantifying glucose values fromsuch sensor measurements having accuracy corresponding to direct bloodglucose measurements. These, as well as other types of devices,generally transmit raw or processed data to remote devices, which caninclude a display, to allow presentation of information to a userhosting the sensor. For example, the DEXCOM G4® PLATINUM SYSTEM WITHSHARE™ continuous glucose monitoring (“CGM”) system and the DEXCOM G5™Mobile CGM system available from DEXCOM, INC. are continuous glucosemonitoring systems that can allow a user to monitor glucose levels. Somesystems and methods that relate to CGM are described in U.S. PublicationNo. 2014/0184422 to Mensinger et al., which is incorporated herein byreference.

SUMMARY

Example implementations described herein have innovative features, nosingle one of which is indispensable or solely responsible for theirdesirable attributes. Without limiting the scope of the claims, some ofthe advantageous features will now be summarized.

Disclosed are techniques, systems, and devices for providing enhancedengagement and remote monitoring experience for a Remote Monitor orgroup of Remote Monitors with a Host or Hosts and/or other RemoteMonitor(s). In some implementations, the disclosed techniques, systems,and devices provide intelligent alerting and/or actionable informationto Remote Monitor(s). In some implementations, one or more remotemonitoring devices and host monitoring devices can be configured (e.g.,through hardware and/or software) to communicate with one another. Eachremote monitoring device can receive data indicative at least in part ofan analyte state (e.g., glucose level) of Host(s) as well as otherdesired information. Host may be using a host monitoring device of ananalyte sensor system (e.g., a continuous glucose monitoring system). Insome cases, a remote monitoring device can communicate with a hostmonitoring device or a server that stores the data of the Host (e.g.,analyte data and other data as described herein).

In some implementations, remote monitoring devices can receive and/ordisplay communications with data that may be cumulative with datacollected by a host monitoring device. In some implementations, remotemonitoring devices and/or host monitoring devices can present data tocontextualize the analyte state of Host(s). Such data can be used atleast in part to further understand the reasons for measurements andalso to perform pattern recognition and/or predictive calculations. Insome implementations, remote monitoring devices and/or host monitoringdevices can transmit data about Remote Monitor(s) (e.g., RemoteMonitor's level of stress or worry, heart rate, blood pressure, overallcondition, etc.) or transmit Remote Monitor-observed data about Host ortransmit Remote Monitor-observed data that affects Host (e.g., observedmood, current weather, amount of homework, etc.) to contextualize atleast in part the analyte state of the host.

In some implementations, remote monitoring devices and/or hostmonitoring devices can classify Remote Monitors. These classificationscan have associated notification settings (e.g., predetermined defaultsettings or user determined settings) based at least in part on theneeds of the host and/or Remote Monitor.

In some implementations, remote monitoring devices and/or hostmonitoring devices can provide intelligent communications representativeat least in part of an event associated with the analyte state of thehost. For example, when an event is triggered, the event can cause acommunication (e.g., alert, notification, message, or othercommunication) to be sent to one or more remote monitoring devices toinform the remote monitoring devices of the event.

In some implementations, a remote monitoring device and/or hostmonitoring device can autonomously manage the communications betweenthemselves based at least in part on treatment information provided bythe host (e.g., whether the host has already administered medicaments).In other embodiments, the communications between remote monitoringdevices and/or host monitoring devices may be triggered based onpredetermined rule settings.

In some embodiments, a method for remote monitoring of a subject'shealth data by authorized monitors includes receiving, at a secureserver, data associated with an analyte state of a host that is providedby a host device operable to receive sensor data generated by acontinuous analyte sensor worn by the host, in which one or more remotemonitoring devices are authorized by the secure server to accesspermissible data of the received data stored on the secure server basedon a set of permissions pre-selected and modifiable by the host for eachremote monitoring device, in which the permissions are associated withwhat data is available to a remote monitoring device once authorized;generating, at the server, a plurality of classifications including afirst classification and a second classification of the remotemonitoring devices authorized to access permissible data, in which aclassification of the remote monitoring devices designates a hierarchyto provide communications based on notifications rules to inform anauthorized remote monitoring device about the host's analyte state; andassigning, at the server, each of the remote monitoring devices to oneof the plurality of classifications, in which the second classificationincludes one or both of (i) greater restrictions to the permissible datathan that of the first classification, and (ii) more restrictivenotification rules than the first classification.

In some embodiments, a method for remote monitoring of a subject'shealth data by authorized monitors includes receiving, at a secureserver, data associated with an analyte state of a host that is providedby a host device operable to receive sensor data generated by acontinuous analyte sensor worn by the host, in which a plurality ofremote monitoring devices are authorized by the secure server to accesspermissible data of the received data stored on the secure server basedon a set of permissions pre-selected and modifiable by the host for eachremote monitoring device, in which the permissions are associated withwhat data is available to a remote monitoring device once authorized;providing, by the server, an alert informative of an event associatedwith the analyte state of the host to selected remote monitoring devicesbased on notification rules that define circumstances to send the alertto a respective remote monitoring device, in which the notificationrules are modifiable by the authorized remote monitoring devices withina scope of the set of permissions to the data associated with therespective remote monitoring device; receiving, at the server, aresponse from one or more of the selected remote monitoring device; andprocessing, by the server, the received response to determine theability or inability of the selected remote monitoring devicecorresponding to the received response to react to the alert.

In some embodiments, a method for remote monitoring of a subject'shealth data by authorized monitors includes receiving, at a secureserver, data associated with an analyte state of a host that is providedby a host device operable to receive sensor data generated by acontinuous analyte sensor worn by the host, in which a plurality ofhost-designated remote monitoring devices are authorized by the secureserver to access permissible data of the received data stored on thesecure server based on a set of permissions pre-selected and modifiableby the host for each host-designated remote monitoring device, in whichthe permissions are associated with what data is available to a remotemonitoring device once authorized; receiving, by the server, locationinformation of the host-designated remote monitoring devices and thehost device; determining, by the server, the ability or inability ofeach of the host-designated selected remote monitoring devices to reactto an alert informative of a dangerous event associated with the analytestate of the host based on a proximity of a host-designated selectedremote monitoring device to the host device within a predetermineddistance; upon the determining the inability of all of thehost-designated selected remote monitoring devices to react to an alert,assigning, by the server, a universal remote monitoring device not amongthe host-designated selected remote monitoring devices, in which theassigning includes generating a set of notifications rules pertaining tocircumstances to send a message to the universal remote monitoringdevice informative of the dangerous event associated with the analytestate of the host.

In some embodiments, a method for remote monitoring of a subject'shealth data by authorized monitors includes receiving, at a secureserver, data associated with an analyte state of a host that is providedby a host device operable to receive sensor data generated by acontinuous analyte sensor worn by the host, in which one or more remotemonitoring devices are authorized by the secure server to accesspermissible data of the received data stored on the secure server basedon a set of permissions pre-selected and modifiable by the host for eachremote monitoring device, in which the permissions are associated withwhat data is available to a remote monitoring device once authorized,and in which the one or more remote monitoring devices are assignednotification rules that define circumstances to send a message to arespective remote monitoring device informative of an event associatedwith the analyte state of the host, in which the notification rules aremodifiable by the authorized remote monitoring devices within a scope ofthe set of permissions to the data associated with the respective remotemonitoring device; processing, by the server, an alert informative of adangerous event associated with the analyte state of the host, in whichthe processed alert is within a set of notification rules associatedwith at least one of the authorized remote monitoring devices;receiving, by the server, an instruction to suppress sending the messageassociated with the alert to the at least one of the authorized remotemonitoring devices; and suppressing, by the server, the sending of themessage to the at least one of the authorized remote monitoring devices.

In some embodiments of the present technology, a method for remotemonitoring of a subject's health data by authorized monitors includesreceiving, at a secure server, data associated with an analyte state ofa host that is provided by a host device operable to receive sensor datagenerated by a continuous analyte sensor worn by the host, in which oneor more remote monitoring devices are authorized by the secure server toaccess permissible data of the received data stored on the secure serverbased on a set of permissions pre-selected and modifiable by the hostfor each remote monitoring device, in which the permissions areassociated with what data is available to a remote monitoring deviceonce authorized; providing, by the server, a notification informative ofan event associated with the analyte state of the host to selectedremote monitoring devices based on notification rules that definecircumstances to send the notification to a respective remote monitoringdevice, in which the notification rules are modifiable by the authorizedremote monitoring devices within a scope of the set of permissions tothe data associated with the respective remote monitoring device; andproviding, by the server, contextual information with the notification,the contextual information including a time, an amount, and/or a type of(i) a medicament taken by the host, (ii) a food or drink ingested by thehost, (iii) an exercise or activity undertaken by the host, (iv) a levelof stress experienced by the host, or (v) an environmental conditionexperienced by the host, or a combination of (i)-(vi) thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed aspects will hereinafter be described in conjunction withthe appended drawings, provided to illustrate and not to limit thedisclosed aspects, wherein like designations denote like elements.

FIGS. 1A and 1B illustrate flow charts describing example processeswhere a host monitoring device and a remote monitoring device receive,process, and transmit data, respectively.

FIG. 2 illustrates a block diagram of an example host monitoring device.

FIG. 3 illustrates a block diagram of an example remote monitoringdevice.

FIG. 4 illustrates a diagram of an example host monitoring devicecommunicatively coupled to remote monitoring devices.

FIG. 5 illustrates an example extended system having a plurality of hostmonitoring devices and remote monitoring devices communicatively coupledthrough a network.

FIG. 6 illustrates an example page showing Host information that can bedisplayed on a remote monitoring device.

FIG. 7A illustrates an example display showing additional data regardingHost analyte measurements.

FIGS. 7B-C illustrate example communications that can be sent between ahost monitoring device, remote monitoring device, and/or other devices.

FIG. 8 illustrates a graphical depiction of an example system having ahost monitoring device, a plurality of remote monitoring devices, asecure server, and networks.

FIG. 9 illustrates a diagram showing example signals transmitted betweena host monitoring device, network(s), and a remote monitoring device.

FIG. 10 illustrates a predictive calculation based at least in part onmeasured data of a Host.

FIG. 11 illustrates an example log that can be displayed for a datapoint on the graph of FIG. 10.

FIG. 12 illustrates an example page showing information about RemoteMonitors.

FIGS. 13A-D illustrate historical Host data overlays that can be viewedwith Host data.

FIGS. 14A-D illustrate example interactions of different classificationsof Remote Monitors.

FIG. 15 illustrates an example classification of Remote Monitors wheredifferent classifications of Remote Monitors receive different amountsand/or different kinds of data.

FIGS. 16A-D illustrate an example display allowing the selection of aclassification for a Remote Monitor and configuration of other settings.

FIGS. 17A-D illustrate example customizable features of a Remote Monitorclassification definition.

FIG. 18A illustrates an example where a Host communicates with aUniversal Remote Monitor in close proximity for assistance.

FIG. 18B illustrates an example where communications can be suppressedbased on proximity.

FIG. 19 illustrates an example situation where a Host can preempt acommunication before it is sent to a Remote Monitor.

FIG. 20 illustrates an example Remote Monitor Response Log showing how aRemote Monitor responded to communications.

DETAILED DESCRIPTION

Various aspects of the systems, apparatuses, and methods disclosedherein are described more fully hereinafter with reference to theaccompanying drawings. This disclosure can, however, be embodied in manydifferent forms and should not be construed as limited to any specificstructure or function presented throughout this disclosure. Rather,these aspects are provided so that this disclosure will be thorough andcomplete, and will fully convey the scope of the disclosure to thoseskilled in the art. Based on the teachings herein, one skilled in theart should appreciate that the scope of the disclosure is intended tocover any aspect of the systems, apparatuses, and methods disclosedherein, whether implemented independently of, or combined with, anyother aspect of the disclosure. For example, an apparatus can beimplemented or a method can be practiced using any number of the aspectsset forth herein. In addition, the scope of the disclosure is intendedto cover such an apparatus or method that is practiced using otherstructure, functionality, or structure and functionality in addition toor other than the various aspects of the disclosure set forth herein. Itshould be understood that any aspect disclosed herein can be implementedby one or more elements of a claim.

Although particular aspects are described herein, many variations andpermutations of these aspects fall within the scope of the disclosure.Although some benefits and advantages of the preferred aspects arementioned, the scope of the disclosure is not intended to be limited toparticular benefits, uses, and/or objectives. The detailed descriptionand drawings are merely illustrative of the disclosure rather thanlimiting, the scope of the disclosure being defined by the appendedclaims and equivalents thereof.

Data from sensor devices, such as analyte monitors like CGM, can providedesirable information to caregivers, clinicians, and/or others who careabout a diabetic person or individual monitoring characteristics of ahealth-related condition, which is sometimes referred to in thisspecification as the “Host.” Typically, a Host monitors suchcharacteristics using a host monitoring device, also referred to as a“host device,” such as a computing device including a smartphone or thelike as part of a larger monitoring system, such as an analytemonitoring system (e.g., CGM). However, many existing analyte monitoringsystems presently suffer from constricting limitations on the amount andtypes of information and engagement shared between a Host and otherindividuals or groups that can remotely monitor characteristics of theHost, which are referred to in this specification as “Remote Monitors.”Remote Monitors remotely monitor the characteristics of the Host using aremote monitoring device, such as a computing device including asmartphone having a software application operating thereon to providethe remote monitoring functionality for the remote monitor user.

In one example, a continuous analyte monitoring system of the Host caninclude one or more body-worn medical devices that can each generatedata and provide the data to a mobile electronics device, such as asmartphone, tablet, smartwatch, or other wearable and/or mobilecomputing device. A smartphone is used in the following example andother examples described. The smartphone can include a dedicatedapplication that configures the smartphone to receive and process thedata provided (e.g., wirelessly transmitted) by the body-worn medicaldevice(s). For example, the data provided by the body-worn medicaldevice(s) can include glucose measurements, insulin delivery amounts,diagnostic information about the medical devices and timestampsassociated with each. The smartphone, using the dedicated application,can then perform various functions based on the received data, such asgenerate charts and user perceptible-alarms using the data. Similarly,for example, the smartphone, using the dedicated application, canreceive formatted or partially formatted data to produce charts, alarms,and other features based on the acquired data of the continuous analytesensor device. The smartphone, using the dedicated application, may alsoreceive and generate other data, such as data from a user of thesmartphone (e.g., user identifying information), user interactions withthe dedicated application, dedicated application diagnostic information,and the like. In some embodiments of the present technology, thecontinuous analyte monitoring system may include a suite of dedicatedapplications operable on one or more computing devices of the Host andon one or more computing devices of Remote Monitors to monitor theHost's analyte state and/or manage access to the Host's data acquired bythe medical device(s).

As engaging platforms expand and incorporate a plurality of RemoteMonitors, additional challenges arise. Present technology does notprovide the desired communication channels and/or functionality toaccommodate sophisticated networks of people (e.g., groups of Host(s)and/or Remote Monitor(s)). For example, different Remote Monitor(s) canhave different roles and responsibilities as to Host(s) and,consequently, desire different information and/or privileges as toHost's health data (e.g., including analyte data) and sensor device(s)(e.g., including an analyte monitor, such as CGM). Remote Monitor(s) forthe same Host can also desire to communicate with each other regardingthe Host and/or each other.

Moreover, while alerts about Host's glucose concentration in somecurrent technologies can inform Remote Monitor(s) of a concerning eventabout the Host's condition, some minimally informative alerts can causeincreased stress and worry by the Remote Monitor(s) that is detrimentalto both Remote Monitor(s) and the Host alike, or worse, these alerts mayaffect the chances of latent action or inaction by the Remote Monitor(s)that might have otherwise been different had the Remote Monitor(s)received more comprehensive and contextual information. For example,Remote Monitor(s) can desire only certain kinds and amounts ofinformation and become irritated by too many or too few kinds and/or toomuch or too little amounts of information. Too much information, forsome Remote Monitor(s), may cause certain desirable information to getlost or ignored. Too little information can cause Remote Monitor(s) notto receive desired information or distrust the integrity ofcommunication systems and/or monitoring systems. As a result, manyexisting analyte monitoring systems fail to create an engaging platformthat enable and/or encourage efficient, communicative interactionsbetween Host(s) and Remote Monitor(s) that can enhance the role ofRemote Monitor(s) in a Host's health management while reducinginterruptions and/or interferences in that Host's life. These currenttechnologies also do not provide the desired level of communicationcustomizability and/or management to accommodate expanded networks ofHost(s) and/or Remote Monitor(s). Accordingly, there is a need forimproved systems and methods for remote and host monitoringcommunication.

Additionally, many conventional monitoring systems can be burdened bylarge amounts of communication traffic (e.g., between host monitoringdevices, remote monitoring devices, and/or servers) across theirnetworks. In some cases, these networks can become overloaded withuntimely and/or unwanted communications that drain network resources. Insome cases, such drains can slow down the networks, cause networkfailures, and/or increase the cost of running the networks. Accordingly,there is a need for improved communications that effectively utilizenetwork resources. For example, by selectively and/or contextuallytransmitting communications, as will be described in this disclosure,monitoring systems can reduce the number of transmissions and/or utilizenetwork resources where they are effective and/or desired. In someimplementations, contextual communications may include slightly largerdata-sizes per transmission, but can also reduce the number oftransmissions that may otherwise bog down networks.

In some cases, selective and/or contextual communications that focus onrelevant data can enhance processing at remote and/or host monitoringdevices. Such communications can also facilitate display of and/or userinteraction with communications. For example, by reducing the number ofcommunications to a remote monitoring device, the remote monitoringdevice can have fewer items to process, and can thereby utilize itsresources more effectively, and sometimes more quickly. Furthermore,with fewer items to display, remote monitoring devices and/or hostmonitoring devices can more effectively engage users by notover-stimulating them with notifications, alerts, and/or other displays.

Moreover, many conventional monitoring systems are no more than passivedisplays of Host's present and/or historical health measurements.Therefore, it would be beneficial to provide Hosts, and/or those whointeract and/or care for Hosts (e.g., Remote Monitors), usefulinformation that can facilitate Host care. For example, as will bedescribed herein, methods that can recognize patterns in Hosts' behavior(and/or the behavior of those who impact Host, such as Remote Monitors)can allow for enhanced care of Host by giving context to Host's healthmeasurements, such as Host's estimated glucose levels. In some cases,predictive calculations can further help Hosts, Remote Monitors, and/orother users understand and anticipate changes in Hosts' health.

In some cases, as networks of host monitoring devices and/or remotemonitoring devices become larger, it can become difficult to organizethe data and/or communications between them in a way that isadministrable. As a result, many conventional monitoring systems are notuser-friendly, and/or provide copious amounts of data without a workableoperative framework. Accordingly, there is a need for ways to organizecommunications and/or data from host monitoring devices and/or remotemonitoring devices. For example, as will be described in thisdisclosure, classifications, interfaces, data logs, discussion logs,and/or other structures can assist in organizing data in a frameworkthat can be controlled, segmented, and/or searched.

In some cases, it can be difficult for a Host to observe and/or monitorcertain characteristics of him/herself. Such characteristics may not bereadily observable by the Host's perception, and/or may be continuouslychanging and/or too difficult (and/or onerous) to repeatedly observe. Insome cases, a Host may be under the care of others due to healthconditions, age, competency, convenience, and/or other reasons. TheseCaretakers may desire to be able to observe and/or monitorcharacteristics of the Host.

Implementations described herein can include systems and methods for oneor more Remote Monitors to remotely monitor characteristics (e.g.,health characteristics) of one or more Hosts. Hosts can include anyentity whose one or more characteristics (e.g., a health characteristic)can be measured using a sensing device, for example, an analyte monitor,like a continuous glucose monitor. These Hosts can include, children(e.g., babies, infants, toddlers, and/or small children), teenagers,young adults, adults, middle-aged person, elderly, and/or any otherperson. In some cases, Hosts can also include non-humans, such as pets,animals, organics, experimental environments (electronic or physical),and/or any system in which measuring an analyte state is desirable.Hosts can be identified (e.g., by name, username, identification number,nickname, etc.) or anonymous with respect to Remote Monitors.

Embodiments in accordance with aspects of the disclosed remotemonitoring technology are perceived to improve operations of the systemsand devices that implement the remote monitoring technology, forexample, by reducing complexities in data processing and datatransmissions between devices, reducing the amount of data andprocessing algorithms to be stored and operated, and thereby speeding upthe performance of the systems as described herein. Moreover,implementations in accordance with such aspects of the presenttechnology are envisioned to improve the ability of users to managetheir diabetes or other disorders with continuous analyte monitoring.

Remote Monitors can include any entity that can remotely monitor on itsdevices characteristics of a Host measured by Host device(s). RemoteMonitors can include any of the aforementioned example entitiesdescribed with respect to Hosts. Remote Monitors can also includeelectronic systems configured to monitor a person's health, such ashospital computer systems, medical databases, hospital beds, medicalrobots, personal health monitors, automated health systems, and thelike. Remote Monitors can also be Hosts, where Remote Monitorsthemselves have host monitoring devices which can measure theircharacteristics using an analyte monitor, such as a CGM.

Generally, Remote Monitors can have a particular role with respect to aHost. For example, Remote Monitors can include Caretakers of the Host,such as parents, spouses, relatives, guardians, significant others,teachers, health practitioners, etc. These Caretakers can take certainresponsibilities in the health and well-being of monitored Hosts. Insome cases, Caretakers can be those who actively take care of the Hostand assist the Host when the Host is in need. As another non-limitingexample, Remote Monitors can include Social Associates of Host(s),including friends, acquaintances, persons in the same social network,persons in the same geographic area, and/or persons connected by one ormore degrees of separation from any of the aforementioned SocialAssociates. These Social Associates may have some interest in theactivities and/or health characteristics of a Host, but ultimately maynot take on the kinds of responsibilities a Caretaker might. As anothernon-limiting example, Remote Monitors can also be Strangers andotherwise personally unknown to a particular Host. Such Strangers couldinclude emergency healthcare professionals, concerned citizens,researchers, and/or others who may desire to learn about and/or assistHosts, even those who could be personally unknown to them. As anothernon-limiting example, Remote Monitors can include Watchers of Host(s).In a non-limiting example, Watchers can include any interested persontemporarily watching a Host in the same or similar manner as aCaretaker, but may not be a Caretaker. Watchers can be contextual (e.g.,based at least in part on proximity and/or activity), such asco-workers, other students, teachers, school program operators,administrators, friends, etc. As another non-limiting example, AssignedRemote Monitors can include any one assigned, for whatever reason, to bea Remote Monitor of a Host. As another non-limiting example, UniversalRemote Monitors can be persons who provide assistance when there are noother Remote Monitors available or other Remote Monitors are too far toassist in a timely manner. These can be concerned citizens and/or anypersons who desire to be of assistance.

For example, when the analyte state of a host drops to a dangerous levelor other health issues arise and no designated Remote Monitor are inclose proximity to provide assistance, the host remote monitoring devicecan emit a beacon to devices in the vicinity of Host, which may becapable of receiving the beacon. The beacon can be transmitted via aBluetooth or other wireless signal as described herein. In addition oralternatively, the beacon can be transmitted by a server or othercomputing device using a cloud-based system with GPS coordinates. Insome embodiments, the cloud-based system can map a distance radiusaround the GPS coordinates of the Host to determine proximity of devicesand presumably owners of those devices who may be in a position toassist the Host. Individuals receiving this beacon on their respectivereceiver devices can receive an alert that someone physically close tothem may need urgent assistance. A map of the area can be provided tothe receivers identifying the location of the individual in need ofassistance. For example, if the receiver device is a smart-glassesdevice, a heads-up-display (HUD), or other smart device, an augmentedreality may be presented to the individual receiver to assist them inlocating the patient in need of help. The receiver individual can scanthe horizon with their augmented reality display and see a virtualidentifier at or near the location of the person in need of assistance.For example, a red blinking dot can be displayed in the augmentedreality through a HUD.

In some environments, individuals near or around a Host may not know howto assist an unresponsive diabetic patient. For example, in an airplane,the flight attendants may lack the training to assist a diabetic patientgenerally or may lack the data to assist a diabetic individual in need.In one embodiment, passive monitoring of wireless signals (e.g.,Bluetooth or other wireless communication as described herein) can beimplemented to listen for emergency calls. A CGM system can send aspecial Bluetooth (or other wireless communication) call in case of ahealth emergency (e.g., low glucose value). The passive monitoringsystem can alert the individuals nearby (e.g., flight attendants) andprovide them with data and information to handle the emergency.

In some cases, Universal Remote Monitors can also be designated RemoteMonitors who are qualified people to treat diabetic conditions, and/orany other conditions relevant to the Host and/or Universal RemoteMonitor. As will be described in this disclosure, in some cases, Hostsand/or Remote Monitors can classify Remote Monitors based on the RemoteMonitors' roles. Such classifications (also called classes) can be usedto define the Remote Monitor's rights, privileges, and/or frequency ofcommunication with Hosts and with other Remote Monitors.

In some cases, it can be desirable for a Host to be able to transmitdata (e.g., raw and/or processed) to one or more Remote Monitor(s) basedon data measured by an analyte sensor and/or other devices of the Hostand/or Remote Monitor. Advantageously, transmitting such information canallow a level of communication and/or coordination that may not beachievable in present systems.

As used throughout this disclosure, normal glucose levels can bedetermined for each individual by consultation with his/her doctor orotherwise, and can be dependent on factors such as whether theindividual has eaten or not, the individual's activity, and/or the timeof day. By way of illustrative example, typical glucose levels of ahealthy adult can be between 72 mg/dL and 108 mg/dL (4 to 6 mmol/L). Thenormal concentration of glucose in the blood of an adult in the morningon an empty stomach can be between 68 mg/dL and 108 mg/dL (3.8 and 6.0mmol/L). Two hours after consuming foods or drinks rich incarbohydrates, the normal concentration of glucose in the blood of ahealthy adult can be between 120 and 140 mg/dL (6.7 and 7.8 mmol/L). Forchildren up to 6 years of age, normal glucose levels before eating canbe between 100 mg/dL (5.5 mmol/L) and 180 mg/dL (10 mmol/L). Beforesleep, normal glucose concentration can be between 110 mg/dL (6.1mmol/L) and 200 mg/dL (11.1 mmol/L). For children between the age of 6and 12, before eating, normal glucose concentration can be between 90mg/dL (5 mmol/L) and 180 mg/dL (10 mmol/L). Before sleep, normal glucoseconcentration can be between 100 mg/dL (5.5 mmol/L) and 180 mg/dL (10mmol/L).

As used herein, remote monitoring devices can be devices used by RemoteMonitors to remotely monitor characteristics of a Host. Throughout thisdisclosure, reference will be made to the functionality and/or structureof remote monitoring devices. Such functionality and/or structure can beinstantiated in hardware and/or software. For example, suchfunctionality and structure can represent physical hardware that ishardcoded to perform such functionality. As another example, remotemonitoring devices can run software that performs such functionalityand/or has such structure. In some implementations, such software canrun computer-implemented methods to create functionality. In some cases,remote monitoring devices can run a software application, such as amobile application, also referred to as an “app,” (e.g., a mobileapplication downloaded from an entity that created and/or owns and/orlicenses the app, and/or an app store such as from APPLE, INC. or GOOGLEINC., or other), that performs the functionality and/or has thestructure described.

Similarly, as used herein, host monitoring devices are devices used byHosts to monitor characteristics of the Host. Throughout thisdisclosure, reference will be made to the functionality and/or structureof host monitoring devices. Such functionality and/or structure can beinstantiated in hardware and/or software. For example, suchfunctionality and structure can represent physical hardware that ishardcoded to perform such functionality. As another example, hostmonitoring devices can run software that performs such functionalityand/or has such structure. In some implementations, such software canrun computer-implemented methods to create functionality. In some cases,host monitoring devices can run a software application, such as a mobileapplication (e.g., a mobile application downloaded from an entity thatcreated and/or owns and/or licenses the app, and/or an app store such asfrom APPLE, INC. or GOOGLE INC., or other), that performs thefunctionality and/or has the structure described.

FIGS. 1A-B illustrate flow charts describing example processes where ahost monitoring device and a remote monitoring device receive, process,and/or transmit data, respectively. In some implementations, theprocesses (e.g., Processes 100, 150) described with respect to a hostmonitoring device and/or a remote monitoring device can be performed bya server (e.g., a secure server) in communication with one or both ofthe host monitoring device and remote monitoring device.

FIG. 1A illustrates example Process 100 where a host monitoring deviceand/or server can receive, process, and/or transmit data, e.g.,information, symbols, measurements, communications, and/or any datadescribed in this disclosure. In some cases, a host monitoring devicesubstantially similar to Host Monitoring Device 200 (FIG. 2) and/or anyhost monitoring devices described in this disclosure can perform Process100. In some embodiments, Process 100 can be performed by a server(e.g., Secure Server 504), in the alternative or in addition to a hostmonitoring device. In some embodiments of Block 102, the host monitoringdevice can receive data from analyte sensor(s), remote monitoringdevice(s), and/or other device(s). In some embodiments of Block 102, theserver can receive data from a transmitter unit of the analyte sensordevice(s), the host monitoring device (e.g., smartphone of Host, whichmay initially receive the data from the analyte sensor device(s)), theremote monitoring device(s), and/or other device(s). By way ofillustrative example, the analyte sensors can be part of a CGM thatmeasures a Host's glucose levels (e.g., an estimated glucose value(“EGV”)). The analyte sensor can be a component of a host monitoringdevice, or a separate component that is not a component of a hostmonitoring device. Advantageously, a CGM can allow a Host to measure theglucose concentration of his/her blood. In some cases, the CGM cantransmit data to a secure server.

Data received in Block 102 can include communications from sensor(s),remote monitoring device(s), and/or other devices. Such communicationscan include notifications, alerts, alarms, messages, and/or any othersort of communication desirable. Data can be received through wiredand/or wireless connections. By way of illustrative example, a processorcan receive data through wired and/or wireless connections. For example,wireless connections can include a transmission protocol such asBluetooth, ZigBee, Wi-Fi, induction wireless data transmission, radiofrequencies, radio-frequency identification (“RFID”), near-fieldcommunication (“NFC”), global system for mobile communications (“GSM”),infrared, and/or any other form of wireless data transmission. Wiredconnections can include any wire with a signal line. For example, suchwires with signal lines can include cables, such as Ethernet cables,coaxial cables, Universal Serial Bus (“USB”), firewire, datalines, wire,and/or any wired connection known in the art. Wired and/or wirelessconnections can also include combinations of any of the aforementioned.Such wired and/or wireless connections can be received by a receiverand/or a transceiver. For example, a host monitoring device can have areceiver and/or transceiver. As another non-limiting example, a server(e.g., secure server) can have a receiver and/or transceiver.

However, in some cases, more information than just an analytemeasurement may be desirable. For example, in the case of measuringglucose levels, many current technologies do not put such glucosemeasurements into a contextual framework that allows for greateranalysis. Advantageously, having such an analysis can reveal more abouta Host's conditions, treatments, and responses that can allow forimproved response predictions and enhanced therapies. The receivedinformation in Block 102 can include Contextual Data relevant to theHost, such as data from remote monitoring device(s) and/or otherdevices.

Contextual data can be provided with alarms or notifications to Hostsand/or Remote Monitors. For example, as described herein, a server canrelay or generate a notifications based on notification rules thatdefine circumstances under which notifications are sent to remotemonitoring devices. The notification can include information, data orcircumstances associated with the analyte state of Host. The server canprovide the notifications with the contextual information. The servercan also provide notifications to Host along with contextual data aboutone or more Remote Monitors.

In the case of a diabetic host, received data can include ContextualData such as data and/or information that may be associated with “why” ameasured analyte, such as glucose levels, occurs and/or behaves as itdoes (e.g., why the glucose levels are, or are trending, in a certainway). Such received information can be measured by the aforementionedanalyte sensor(s), measured by other devices internal or external to theHost, manually inputted by the Host, received by remote monitoringdevice(s), or otherwise inputted into the host monitoring device.Contextual Data can also be inputted by a Remote Monitor on a remotemonitoring device and/or host monitoring device. For example, ContextualData can include data inputted by Remote Monitor(s) about a Host. Inaddition to being able to be received by Remote Monitor(s), ContextualData can also be about the Remote Monitor(s). Contextual Data can alsoinclude information about the Remote Monitor(s) that can be indicativeof the health, awareness, availability, etc. of Remote Monitor(s) toassist a Host.

In some implementations, this Contextual Data can include, (i)time/amount/type of medicament taken (e.g., insulin, sulfonylureas,biguanids, meglitinides, thiazolidinediones, DPP-4 inhibitors, SGLT2inhibitors, alpha-glucosidase inhibitors, bile acid sequestrants, and/orother drugs or treatments), (ii) time/amount/type of food ingested(e.g., carbohydrates, protein, dairy, fat, fruits, vegetables, candy,dessert, sugars, calories, quantities, preparations, etc.), (iii)time/amount/type of exercise or physical activity undertaken (e.g.,engaging in sports, running, walking, swimming, skiing, snowboarding,skateboarding, biking, weight lifting, sitting, sleeping, being idle,resting, etc.), (iv) level of stress felt (e.g., acute, episodic acute,emotional, chronic, high stress, medium stress, low stress, no stress,anxiety, panic attack, etc.), (v) environmental conditions (e.g.,weather, humidity, pressure, temperature, scenery, location or situationincluding being at work, at school, on break or on vacation, etc.), (vi)time of day, and/or (vii) other measurements, and/or patterns and/orcombinations of any of the aforementioned. Accordingly, notificationscan be provided with contextual data as described herein.

As described herein, notification rules, sets of permissible data,access and authorization rules can be generated or assigned based onRemote Monitor's classification. Some classification entail higherprivileges, priorities, and responsibilities than other classificationsand accordingly receive greater access, more notifications and otherprivileges and duties as described herein. Other classifications mayentail fewer privileges, priorities and responsibilities and accordinglyreceive greater restrictions to the permissible data than higherpriority classifications and/or more restrictive notification rules thanthe higher priority classifications. In some embodiments, prior toproviding contextual data, the classification of Remote Monitor may bedetermined. If a Remote Monitor's respective remote monitoring device isassigned to a higher priority classification, then notifications, alertsor communications are provided with contextual data. If the respectiveremote monitoring device is assigned to a lower priority classification,then notifications, alerts or communications are provided with limitedor no amount of contextual data.

Additionally, there can be different categories of Contextual Data. Inmany conventional devices, such information can be difficult toidentify, locate, communicate, and/or analyze. Advantageously, someimplementations of the present disclosure can categorize Contextual Datain advantageous and/or non-intuitive ways. Some categories may be ofmore interest to some Remote Monitor(s), Host(s), and/or others, whereassome categories may be of less interest. These categories can be used tosort and/or identify data for Remote Monitor(s), Host(s), and/or othersin some implementations. In some implementations, the data for suchcategories can be viewed by itself as a category, and/or viewed withother categories together. In some implementations, no categories may beused to sort data. By way of illustrative example, some categories ofreceived Contextual Data can include Health Data, System Data, TreatmentData, User Data, and Sensor Data. Accordingly, in some embodiments, thescope and amount of providing the contextual data can depend onpredetermined categorizations, which may be determined by a Host or ahost monitoring device, automatically by the device, or aspre-designated input by a Host.

Health Data can include, insulin intake and administration (e.g., basalor bolus), type of insulin, exercise, stress, illness (e.g., those thatcan affect insulin/carbohydrate ratios), form of diabetes, other chronicconditions, and/or other characteristics (e.g., permanent or temporary)of a Host and/or Remote Monitor. In some implementations, Health Datacan include data generated by a bolus calculator that makes suggestionson bolus administration. The bolus calculator can estimate the bolusdesired to cover any carbohydrates eaten or drank in order to correcthigh glucose. Such data can be estimated for a Host and/or RemoteMonitor to determine bolus administration, if any, which could betherapeutically beneficial.

System Data can include, system errors, alerts, statuses, warnings,and/or other information related to a host monitoring device, anotherdevice of the Host, server (e.g., secure servers and/or servers such asthose implementing notification services), workstation, remotemonitoring device, and/or another device of Remote Monitor(s).Non-limiting examples of System Information can include statuses,reservoir levels of sensors, battery statuses, calibrations, occlusiondetection, use logs, histories, power on/off, failures, etc.

Treatment Data can include, prepopulated and/or user-inputtedinformation about a treatment administered and/or that will beadministrated. This prepopulated and/or user-inputted information caninclude a statement of acknowledgement of condition (e.g., acknowledgingglucose level, future glucose levels, activities, communications, and/orany information that might be available to a Host and/or Remote Monitor,including, but not limited to, those from the host monitoring device,remote monitoring device(s), and other devices), a future or pasttreatment, and any other information the Host might desire to add forhimself/herself or a Remote Monitor. By way of illustrative example,Treatment Information can include a statement such as, “I responded tomy low alert. Ate 15 grams of carbs. No need to panic.”

User Data can include data based on data from a Host and/or RemoteMonitor(s). User Data can include, user-inputted information, such asdescriptions of treatments, activities, observations, schedules,reactions, emotions, thoughts, notes, etc. User Data can also includedata based on information and/or data in a Host's and/or RemoteMonitor's calendars, messages, email, social media, Global PositioningSystems (“GPS”), and/or any other program or application used by Host(s)and/or Remote Monitor(s). User data can also include data that can beconfigured to be used with other applications of Hosts and/or RemoteMonitor(s), including, calendars, messages, email, social media, GPS,and/or any other program or application used by Host(s) and/or RemoteMonitor(s). As a non-limiting example, user data can include calendarinformation instructing a viewer to look at the Host's information at aparticular day and/or time.

In some cases, a Remote Monitor can input information about a Host,and/or the Host about the Remote Monitor, as User Data. For example, theRemote Monitor can be a Caretaker of a Host, who may be unable and/orunwilling to input data (e.g., when the Host is a child or elderlyperson). In other situations, the Host and/or Remote Monitor can observeinformation about the other and input that information into either ahost monitoring device or a remote monitoring device, or both. In someimplementations, the Remote Monitor can input ancillary data to a Hostto be included on the display (e.g., on the display graph or other formof data display, of a host monitoring device). The Host can add events(e.g., ate, exercise, insulin dose) to a trend display, such as agraph/reflection view (e.g., a display shown in Block 106). The RemoteMonitor can also be able to add events to make the Host's displaycontextually richer. For example, a Remote Monitor can add observedmood, weather, meeting schedule, homework stress, etc. Other examplesinclude changed basal rate, blood pressure high, started on anotherprescription for another issue, etc. In some cases, a Host can pushinsights to a Remote Monitor about a Host, such as calendar information(e.g., a calendar message saying “Let's look at your Host's day today”and other events). Such inputs can be made using a user interface, suchas any user interface described in this disclosure.

User Data can also include insights about a Host's and/or RemoteMonitor's activities. For example, and without limitation a Host and/orRemote Monitor can input teachable moments, such as insights, notes,feelings, etc. that are written, recorded, and/or selected fromprepopulated options. In some cases, User Data can also includeprocessed information from inputted data. For example, a processor(e.g., a processor communicatively coupled to a host monitoring deviceor a remote monitoring device) can learn teachable moments from theactivities of a Host and/or Remote Monitor. By way of illustrativeexample, the processor can recognize that after taking insulin, theHost's insulin levels go low after eating. A processor can learn thispattern and/or make recommendations to a Host to change the timing ofinsulin, give an alert, or modify, ignore, or elevate any alertsregarding such insulin drops when such happens. By way of anotherillustrative example, after a Host exercises, his/her glucose levels cango low. A processor can learn this pattern and/or make recommendationsto eat before exercising.

Sensor Data can include data based on data collected by sensorsassociated with a Host or Remote Monitor(s). This Sensor Data caninclude, data from health rate monitors, activity trackers, pulseoximeters, wearables (e.g., smart watches, smart rings, workoutmonitors, electrocardiographs, bioimpedence sensors, breathing monitors,sleep monitors, posture monitors, habit detectors, temperature trackers,fabrics embedded with sensors, moisture detectors, etc.),accelerometers, gyroscopes, speedometers, pedometers, blood pressurereaders, pump data for administration of other drugs, drug sensors(e.g., breathalyzers and sensors configured to measure intoxication orpresence of drugs), medical devices, and/or other devices that measure acharacteristic of the Host and/or Remote Monitor(s). In some cases, suchsensor data can be indicative of a Host's and/or Remote Monitor(s)'health. As a non-limiting example, data from an accelerometer canindicate whether a Host and/or Remote Monitor is sleeping, exercising,and/or any other activity. In some cases alerting of Hosts and/or RemoteMonitors can be modified based on such data.

Any of the data mentioned in this disclosure (e.g., analytemeasurements, communications, Processed Data, Contextual Data, HealthData, System Data, Treatment Data, User Data, Sensor Data, Summary Data,and/or other data mentioned in this disclosure) can be retrospectiveand/or actionable. Retrospective Data can include data that is no longerActionable Data. That is, Actionable Data can be data that can be usedwith timeliness sufficient to allow effective action to prevent and/orrespond to a change (e.g., an adverse change) in physiological state ofa Host, Remote Monitor, and/or other user. Actionable Data can beso-called real-time continuous glucose measurements and can also includepredicted continuous glucose measurements (e.g., glucose valuespredicted for a future period in time, such as 5 minutes or an hour intothe future). To illustrate with an example of glucose data, actionablecontinuous glucose measurement data can be glucose measurement data thatcan be used to treat a current clinical diabetic state of a Host, RemoteMonitor, and/or other user, such as impending or actual hypoglycemia, orimpending or actual hyperglycemia. In contrast, retrospective continuousglucose data can be data that would not be used for treating a currentclinical state of a Host, Remote Monitor, and/or other user because thedata can be likely too old to provide value for formulating decisions onhow to treat the Host, Remote Monitor, and/or other user. While possiblynot useful for treating a current clinical state, Retrospective Data canbe still very useful for extrapolating insights into the health of aHost, Remote Monitor, and/or other user. Examples include comparingglucose levels of a patient over time to carbohydrates (“carbs”) and/ormedication ingested by the Host, Remote Monitor, and/or other user togain insights as to how the carbs and/or medication have been affectingthe glucose levels of the Host, Remote Monitor, and/or other user. Insome cases, the insights gained from the retrospective data can be usedto modify a treatment plan associated with the Host, Remote Monitor,and/or other user.

It is understood that what constitutes Actionable Data can depend uponvarious factors. For instance, what constitutes Actionable Data candepend upon how quickly a clinical state of a health conditionassociated with one or more monitored health characteristics can changefrom a non-adverse physiological state to an adverse physiologicalstate. To illustrate, although diabetic clinical states can changerelatively quickly—for example, from being in safe range of glucoseconcentration to an unhealthy range of glucose concentration—thetimeframe for such a change can be typically in the order of longer thanabout 30 minutes. In contrast, a monitored health condition associatedwith a heart condition can change much quicker, in the order of minutesor even seconds. Thus, Actionable Data associated with monitoring adiabetic condition (e.g., continuous glucose data) may extend along alonger timeframe than data associated with monitoring a heart condition(e.g., Electrocardiogram (“EKG”) and heart rate data).

The data received in Block 102 can be Raw Data or Processed Data, orboth. For example, Raw Data can be impedances, currents, voltages,capacitances, bits, impulses, switches, and/or other electrical ormechanical measurements from a sensor that can be processed (e.g.,correlated) to determine a characteristic (e.g., glucose concentrationor any of the aforementioned information). Processed Data can includecharacteristics, measurements, conclusions, communications,descriptions, observations, parameters, statistics, etc. In some cases,data received in Block 102 can be passed directly to Block 108 fortransmission.

In some implementations, Processed Data can include Summary Data, whichcan be derived from received data, including analyte measurements,received communications, Contextual Data, Health Data, System Data,Treatment Data, User Data, Sensor Data, and/or any data described inthis disclosure. By way of illustrative example, Summary Data caninclude a summary number on a scale, such as a health scale. In theexample of Summary Data for Host data, a Host's overall health can berated on a health scale from zero (0) to ten (10), or any other scaledrange as desired. By factoring data received in Block 102, such as oneor more of glucose level, activity, pulse, time of day, etc., SummaryData can give a summary to a viewer (e.g., a Host or Remote Monitor)indicative of the overall health of a Host.

In some cases, it can be desirable to know a Remote Monitor's condition.For example, contextual data about a Remote Monitor may be received at aserver. The contextual data about the Remote Monitor operating a remotemonitoring device can include, for example, time, amount, and/or type of(i) an activity undertaken by the remote monitor user, (ii) a level ofstress experienced by the remote monitor user, or (iii) an environmentalcondition experienced by the remote monitor user, or a combination of(i)-(iii). The emotions, activities, and stresses that the RemoteMonitor experiences may be informative, especially when it can beperceived by a Host and/or can affect the Host's health. In such a case,the Remote Monitor's condition can be a factor that affects an analytemeasurement such as the Host's glucose levels. The condition of theRemote Monitor can also roll back to the health of the Host. The RemoteMonitor's condition can be used to gauge the engagement of the RemoteMonitor as well as predict whether the Remote Monitor is suffering fromalarm fatigue, is likely to assist the Host effectively and timely, etc.As a result, it can be desirable to collect data on the condition of theRemote Monitor, process it, and provide it as Summary Data to the Host,Remote Monitor, or other Remote Monitors. Accordingly, if processing aRemote Monitor's contextual data indicates an inability of the RemoteMonitor to react to alarms or notifications, Host and/or other RemoteMonitors can be provided with Summary Data including at least some ofRemote Monitor's contextual data to alert them.

For example, such Summary Data can include a worry scale of a RemoteMonitor, which can be based on processing Remote Monitor data (e.g.,analyte measurements, communications, Processed Data, Contextual Data,Health Data, System Data, Treatment Data, User Data, Sensor Data,Summary Data, and/or any data described in this disclosure). In someembodiments, the worry scare can include scales from “not scared” to“scared.” In some implementations, the worry scale can account for datarelating to how the Remote Monitor's physiological condition may affectthe health of the Host. Such a worry scale can also analyze the RemoteMonitor's response time and/or behaviors in relation to communications(e.g., does the Remote Monitor close an alert or view an EGV because ofthe alert?). In some cases, the worry scale can range from zero (0) toten (10), or any other scaled range as desired. In this example, a zero(0) on the worry scale can be indicative of little or no worries and aten (10) can be indicative of high or the most worried. Other ways ofscaling the worry scale can also be used (e.g., zero (0) is the mostworried and five (5) is the least worried, and/or any other formatand/or scaling). In some cases an upper threshold can be used with theworry scale where if the Remote Monitor has a rating on the scalegreater than or equal to a predetermined value, communication settings(e.g., communication frequency, privileges, notifications, alerts, etc.)can be changed. In some cases, a lower threshold can be used where ifthe Remote Monitor has a rating on the scale less than or equal to apredetermined value, communication settings can be changed. By way ofexample, a worry scale where zero (0) is not worried and ten (10) isvery worried can have an upper threshold of eight (8). If a RemoteMonitor is measured to have a nine (9) on the worry scale, he/she mayreceive additional notifications (e.g., for even non-critical events).In some cases, the Remote Monitor's classification can change so thatthe Remote Monitor can be elevated to a classification with moreresponsibilities and/or communications. In some implementations, theopposite may be true where an over-worried Remote Monitor is seen as notbeing fit to take care of a Host. In such a case, the Remote Monitor'scommunication settings may be changed so that he/she receives fewercommunications (e.g., only important notifications and/or none at all),and/or the Remote Monitor can be moved in classification so that he/shehas fewer responsibilities and/or communications.

In Block 104, the received data from Block 102 can be processed. Block104 can also receive other data from Blocks 106, 108, as will later bedescribed. In implementations of the process in Block 104, the receiveddata can be processed by the host monitoring device and/or the secureserver. In some embodiments, the data received from the analytesensor(s), remote monitoring device(s), and/or other device(s) can bereceived by the host monitoring device, and transmitted to the secureserver to implement the processing of the received data in Block 104. Byway of illustrative example, a processor can receive data through wiredand/or wireless connections, such as any wired and/or wirelessconnections described in this disclosure. Such processor can becommunicatively coupled to the aforementioned analyte sensor(s), remotemonitoring device(s), and/or other device(s) internal or external to aHost, so that data and/or information can be sent between them. In someimplementations, for example, the processor can be included in a server.Sent data can include, any of the data described in this disclosure(e.g., analyte measurements, communications, Processed Data, ContextualData, Health Data, System Data, Treatment Data, User Data, Sensor Data,Summary Data, etc.). Signals can also be sent (e.g., received andtransmitted) between such processor and the aforementioned analytesensor(s), remote monitoring device(s), and/or other devices(s),including any device described with respect to Blocks 102, 106, 108.Non-limiting examples of such signals include interrogative signals,status signals, synchronization signals, timer signals, data, and thelike.

In some implementations, Block 104 can perform signal processing,pattern recognition, and/or any other analysis on the data received fromBlocks 102, 106, 108. In some cases, data can be generated based onreceived data. For example, in the case of a continuous glucose monitor,Block 104 can analyze measurements taken by the continuous glucosemonitor to determine glucose concentration, generate communications(e.g., messages, notifications, alerts, interrogative signals, statussignals, synchronization signals, timer signals, data, information,etc.) based on the measurements and/or received data. Similarly, in thecases of continuous glucose monitor, Block 104 can detect upward ordownward trends in glucose levels, make recommendations, and/or anyother desired information that may be relevant about the Host.

In Block 106, the data (e.g., data generated in Block 104) can bedisplayed. For example, a display can be used, including liquid-crystaldisplays (“LCDs”), light-emitting diode (“LED”) displays, LED LCDdisplays, in-plane switching panels (“IPSs”), cathode ray tubes, plasmadisplays, ultra-high definition (“HD”) panels, 4K displays, retinadisplays, organic LED displays, touchscreens, surfaces, canvases, and/orany displays, televisions, monitors, panels, and/or devices known in theart for visual presentation. The display may be a component of a hostmonitoring device and/or communicatively coupled to a host monitoringdevice. Similarly, the display can be a component of a server and/orcommunicatively coupled to the server.

In some implementations, a user interface can be communicatively coupledto the display (e.g., on a host monitoring device and/or server). Inthis way, a user can input data related to the Host and/or RemoteMonitors. In some implementations, the display and/or user interface candisplay data from Blocks 102, 104, 108 directly or indirectly. Such datacan include, data related to communications, analyte measurements,Processed Data, Health Data, System Data, Treatment Data, User Data,Sensor Data, Summary Data, and/or any other data received in Block 102,processed in Block 104, and/or sent in Block 108. In this way, ifdesirable, a user can input other data (e.g., any additional data),including, but not limited to, reactions to what is displayed on thedisplay. Such inputted data can fall under the category of User Data.This data can be sent to Block 104 for processing. In someimplementations, the information can be sent directly to Block 108 fortransmitting, or sent to Block 102 to inquire more data.

In some implementations, Block 106 can provide adaptive and/orcontextual communication (e.g., alerting, notification, messages, etc.)to a Host. For example, the host monitoring device can use data (e.g.,analyte measurements, Processed Data, Health Data, System Data,Treatment Data, User Data, Sensor Data, Summary Data, and/or any otherdata described in this disclosure) to determine a characteristic of theHost and/or modify alerting behavior accordingly. Similarly, forexample, the determination of a characteristic of the Host and/oridentification of alerting behavior can be processed by the secureserver (e.g., in Block 104) and provided to the host monitoring deviceto present the adaptive and/or contextual communication to the Host. Byway of illustrative example, a host monitoring device can becommunicatively coupled to an accelerometer. Data from the accelerometercan be indicative of movement of the Host, which can allow a hostmonitoring device to determine the activity of a Host, such as whether aHost is sleeping, exercising, and/or any other activity as desired. Thehost monitoring device can then modify the alerting as desired based onthat activity. For example, the Host using the host monitoring devicecan turn down the frequency of communications (e.g., via the dedicatedapplication on the host monitoring device) while the Host is asleep ifthe Host desires to not be disturbed while sleeping. As anothernon-limiting example, data from the accelerometer can be sent to aserver, which can determine the activity of a host. The server canmodify the alerting as desired based on the activity, such as turningdown the frequency of communications while the Host is sleeping. In somecases, the host monitoring device and/or server can turn off non-urgentcommunications. In some cases, the host monitoring device and/or servercan elevate urgent communications and/or increase alert volumes in orderto wake up a Host. As mentioned, other data described in this disclosurecan be used, including, data from calendars, messages, email, socialmedia, GPS, smart watches, applications (e.g., mobile applications),heart rate monitors, activity trackers, pulse oximeters, wearables,accelerometers, gyroscopes, speedometers, pedometers, blood pressurereaders, drug administration data (e.g., pump data), or data from othermedical devices, etc.

In Block 108, data can be transmitted. Such data can be dataaforementioned with respect to Blocks 102, 104, 106, and/or data and/orinformation based on such data. A transmitter, receiver, and/ortransceiver can be used for the transmittal from a host monitoringdevice and/or server. This transmitter, receiver, and/or transceiver canuse a transmission protocol across any wired or wireless connectionmentioned in this disclosure. In some implementations, such data can betransmitted to one or more remote monitoring device(s) either directlyor through a network. Also either directly or through a network, Block108 can transmit data to other device(s), such as other sensor(s), hostmonitoring device(s), mobile devices (e.g., tablets, cellphones,smartphones, e-readers, phablets, and the like), wearables (e.g., smartwatches, smart rings, workout monitors, electrocardiographs,bioimpedence sensors, breathing monitors, sleep monitors, posturemonitors, habit detectors, temperature trackers, fabrics embedded withsensors, moisture detectors, etc.), medical devices, set-top boxes,internet streaming devices, gaming consoles, smart appliances, anydevice with access to the internet and/or any network protocol,computers (e.g., laptops, desktops, personal computers, etc.), and/orany desirable device. In some cases, any of the aforementioned otherdevice(s) may also be remote monitoring devices, servers, and/or hostmonitoring devices.

In some cases, it may be desirable for Remote Monitor(s) to view datafrom Host monitoring device(s), servers, other remote monitoringdevice(s), and/or other device(s). Such information can be desirable forthe Remote Monitor(s) to fulfill a particular role, such as Caretaker,Social Associate, Stranger, Watcher, Assigned Remote Monitor, UniversalRemote Monitor, and/or any other role. FIG. 1B illustrates exampleProcess 150 where a remote monitoring device and/or server can receive,process, and transmit data. In some cases, a remote monitoring devicesubstantially similar to Remote Monitoring Device 300 of FIG. 3, and/orany remote monitoring devices described in this disclosure can performProcess 150. Process 150 can be performed by a server (e.g., SecureServer 504 of FIG. 5), in the alternative or in addition to a remotemonitoring device. In some cases, such a server can be a separate serverthan a server that performs Process 100. In some cases, the same servercan perform Process 100 and Process 150.

In Block 152, the remote monitoring device and/or server can receivedata from host monitoring device(s), remote monitoring device(s),servers, and/or other devices directly or indirectly (e.g., via aserver). The sent or received data can include data related to analyteconcentrations (e.g., glucose levels), communications, Processed Data,Contextual Data (e.g., Health Data, System Data, Treatment Data, UserData, Sensor Data, Summary Data, and other Contextual Data mentioned inthis disclosure), and/or any desirable data. Remote Monitor(s) can beselectively chosen to remotely monitor a Host based on a Host-initiatedinvitation process, such as those described in U.S. Patent PublicationNo. 2014/0184422 to Mensinger et al., which is incorporated herein byreference. Data accessible to the remote monitor device can beauthorized according to a remote monitor authorization process, such asthose described in U.S. Patent Publication No. 2014/0184422 to Mensingeret al.

As described, in some embodiments, a Host's CGM device can transfer theHost's data to a secure server. An authorized Remote Monitor can accessthe Host's data on the secure server. In some cases, if the CGM data isunavailable on the server, the authorized Remote Monitor can issue acommand to request the Host's data from the CGM. For example, in someimplementations the direct command request of the Host's data by theremote monitoring device can use near field communications (NFC) orother wireless protocol to enable communication between the Host's CGMelectronics unit and the remote monitoring device.

A remote monitoring device and/or server can also receive data fromother remote monitoring device(s). In some cases, a plurality ofindividuals can have particular roles (e.g., Caretakers, SocialAssociates, Strangers, Watchers, Assigned Remote Monitors, UniversalRemote Monitors, and/or other roles) with respect to the Host. Abilityto receive and/or transmit data between remote monitoring device(s) canallow for a level of coordinated role fulfillment that is difficult toachieve, or is unavailable with current technology, which may not havethe level of interactivity, coordination, and/or integration ofimplementations described in this disclosure.

A remote monitoring device and/or server can also receive data fromother device(s). For example, it may be desirable to receive informationabout a Remote Monitor to understand how the Remote Monitor may respond,behave, and/or react under certain conditions. By way of illustrativeexample, a Remote Monitor can be one of a plurality of Remote Monitorswho fulfill the role of Caretaker to a Host. There can be a hierarchy ofsuch Caretakers, which will be described in further detail later in thisdisclosure, where one or more Caretakers receive data, information,alerts, notifications, and/or other communications regarding a Hostbefore other Caretakers. In some implementations, one or moreclassifications can be generated, where the classifications designate ahierarchy to provide communications based on notification rules toinform authorized remote monitoring devices about a Host's analytestate. In the case where a particular Caretaker receives data first,that Caretaker can be a Primary Caretaker. As an example, if thatparticular Primary Caretaker is under high stress as evidenced by bloodpressure, pulse, temperature, and/or other measurements and/or data(e.g., analyte measurements, communications, Processed Data, ContextualData, Health Data, System Data, Treatment Data, User Data, Sensor Data,Summary Data, and/or other data mentioned in this disclosure), thatPrimary Caretaker may not be in a position to adequately take care of aHost when the Host is in need. In some cases, that Primary Caretaker'sremote monitoring device and/or a server can receive data indicative ofhigh stress and/or determine (e.g., using a processor of the remotemonitoring device and/or server) that other Caretakers and/or RemoteMonitors should receive information first instead of that PrimaryCaretaker. The priority of which Remote Monitor (e.g., remote monitoringdevice) receives communication first can be determined based on a RemoteMonitor's assigned classification.

Other data from other devices can be used to determine whether a changein classification of a remote monitoring device is warranted. Theseother devices can include, devices that measure data that may berelevant to a Remote Monitor's ability to fulfill a role with respect toa Host. Some non-limiting examples of other devices include sensor(s),mobile devices (e.g., tablets, cellphones, smartphones, e-readers,phablets, and the like), wearables (e.g., smart watches, smart rings,workout monitors, electrocardiographs, bioimpedence sensors, breathingmonitors, sleep monitors, posture monitors, habit detectors, temperaturetrackers, fabrics embedded with sensors, moisture detectors, etc.),set-top boxes, internet streaming devices, gaming consoles, smartappliances, any device with access to the internet and/or any networkprotocol, computers (e.g., laptops, desktops, personal computers, etc.),medical devices, heart rate monitors, activity trackers, pulseoximeters, accelerometers, gyroscopes, speedometers, pedometers, bloodpressure readers, pump data for administration of other drugs,continuous glucose monitors, drug sensors (e.g., breathalyzers andsensors configured to measure intoxication or presence of drugs), and/orany desirable device. In some cases, any of the aforementioned otherdevice(s) may also be remote monitoring devices and/or host monitoringdevices.

In Block 154, the received data from Block 152 can be processed. Block154 can also receive other data from Blocks 156, 158. By way ofillustrative example, a processor (e.g., a processor included in aremote monitoring device and/or server) can receive the data. Suchprocessor can receive the data through wired and/or wirelessconnections, such as any wired and/or wireless connection described inthis disclosure.

Such processor can be communicatively coupled to host monitoringdevice(s), remote monitoring device(s), server(s), and/or otherdevice(s) so that data can be sent, received, and/or transmitted betweenthem. Such sent data can include, any of the data described in thisdisclosure (e.g., analyte measurements, communications, Processed Data,Contextual Data, Health Data, System Data, Treatment Data, User Data,Sensor Data, Summary Data, and/or other data mentioned in thisdisclosure). Signals can also be sent, received, and/or transmittedbetween such processor and the aforementioned host monitoring device(s),remote monitoring device(s), server(s), and/or other devices(s),including any device described with respect to Blocks 152, 156, 158.Non-limiting examples of such signals include interrogative signals,status signals, synchronization signals, timer signals, data, and thelike.

In some implementations, Block 154 can perform signal processing,pattern recognition, and/or any other analysis on the data received fromBlocks 152, 156, 158. For example, such signal processing, patternrecognition, and/or any other analysis can be performed by a remotemonitoring device and/or a server. In some cases, data can be generatedbased on the received data. By way of illustrative example, in the casewhere a remote monitoring device receives a communication regarding aHost based on the Host's glucose levels, Block 154 can process thecommunication and determine whether and how often to alert and/or notifya Remote Monitor based on predefined settings, such as predefinedfrequency of alerts, priority of alerts, availability of Remote Monitor,availability of other Remote Monitor(s), severity of notification,classification of Remote Monitor, position in hierarchy ofclassification of Remote Monitor, and/or other factors. Similarly, insome implementations, a server can receive a communication regarding aHost based on the Host's glucose level. Block 154 can then process thecommunication and determine whether and how often to alert and/or notifyone or more Remote Monitors (e.g., using their remote monitoringdevices) based on predefined settings, such as predefined frequency ofalerts, priority of alerts, availability of Remote Monitor, availabilityof other Remote Monitor(s), severity of notification, classification ofRemote Monitor, position in hierarchy of classification of RemoteMonitor, and/or other factors.

In Block 156, the data (e.g., data from Blocks 152, 154, 158) can bedisplayed. For example, a display can be used, including any displaydescribed in this disclosure. In some cases, such display can be acomponent of and/or communicatively coupled to a remote monitoringdevice. In some cases, such display can be a component of and/orcommunicatively coupled to a server. In some implementations, a userinterface can be communicatively coupled to the display, such as anyuser interface described in this disclosure. In this way, a user caninput User Data related to the Host and/or Remote Monitor(s).

In some implementations, the display and/or user interface can displaydata from Blocks 152, 154, 158 directly or indirectly. Such data caninclude, data related to communications, analyte measurements, ProcessedData Contextual Data, Health Data, System Data, Treatment Data, UserData, Summary Data, and Sensor Data, and/or other data received in Block152, processed in Block 154, and/or transmitted in Block 158. In thisway, if desirable, a user can input other information (e.g., anyadditional information), including, but not limited to, information inreaction to what is displayed on the display. This information can besent to Block 154 for processing, including, but not limited to, thecreation of Summary Data and Processed Data. In some implementations,the information can be sent directly to Block 158 for transmitting, orsent to Block 152 to inquire more data.

In Block 158, data can be transmitted. Such data can be any dataaforementioned with respect to Blocks 152, 154, 156, and/or any databased on such data. A transmitter, receiver, and/or transceiver can beused for the transmittal. This transmitter, receiver, and/or transceivercan use a transmission protocol across any wired and/or wirelessconnection mentioned in this disclosure. In some implementations, suchdata can be transmitted to one or more remote monitoring device(s)either directly or through a network. Also, either directly or through anetwork, Block 158 can transmit data to other device(s), such as othersensor(s), host monitoring device(s), mobile devices (e.g., tablets,cellphones, smartphones, e-readers, phablets, and the like), wearables(e.g., smart watches, smart rings, workout monitors,electrocardiographs, bioimpedence sensors, breathing monitors, sleepmonitors, posture monitors, habit detectors, temperature trackers,fabrics embedded with sensors, moisture detectors, etc.), medicaldevices, set-top boxes, internet streaming devices, gaming consoles,smart appliances, any device with access to the internet and/or anynetwork protocol, computers (e.g., laptops, desktops, personalcomputers, etc.), and/or any desirable device. In some cases, any of theaforementioned other device(s) may also be remote monitoring devicesand/or host monitoring devices.

FIG. 2 illustrates a block diagram of an example host monitoring device200. Host Monitoring Device 200 can include Controller 201, Memory 202,Power Supply 203, and/or Operative Modules 204, each of which can beoperatively and/or communicatively coupled to each other and eachother's components and/or subcomponents. Controller 201 can control thevarious operations performed by Host Monitoring Device 200. In someimplementations, Host Monitoring Device 200 can be configured to performthe example processes, methods, and/or systems, and/or substantiallysimilarly processes, methods, and/or systems, illustrated in FIG. 1A.

Controller 201 can be operatively and/or communicatively coupled toMemory 202, which can include, volatile, non-volatile, read-only memory(“ROM”), and/or random access memory (“RAM”), and can provideinstructions and data to Controller 201. A portion of Memory 202 canalso include non-volatile random access memory (“NVRAM”). Controller 201can perform logical and arithmetic operations based on programinstructions stored within Memory 202. Controller 201 can include one ormore processors (e.g., microprocessors) and other peripherals. Theinstructions in Memory 202 can be executable to implement the methodsdescribed herein. Operative Modules 204 can be coupled to Controller 201to perform the various operations described herein. One or more, ornone, of the modules in Operative Modules 204 can be included in someimplementations. Throughout this disclosure, reference will be made tovarious controllers and/or processors. In some implementations, a singlecontroller (e.g., Controller 201) can serve as the various controllersand/or processors described. In other implementations, differentcontrollers and/or processors can be used. Controller 201 can sendand/or receive signals, such as power signals, control signals, sensorsignals, interrogatory signals, status signals, data signals, electricalsignals and/or any other desirable signals, including discrete andanalog signals. Controller 201 can coordinate and/or manage OperativeModules 204, and/or set timings (e.g., synchronously or asynchronously),turn on/off, control power budgets, receive/send network instructionsand/or updates, update firmware, send interrogatory signals, receiveand/or send statuses, and/or perform any operations for running featuresof Host Monitoring Device 200.

Operative Modules 204 can include various modules that perform functionsfor Host Monitoring Device 200. For example, such modules of OperativeModules 204 can include Sensors 205, Data Storage 209, Locator 206,Communicator 207, User Interface 208, Information Manager 210, and/orSignal Processor 211.

In some implementations, Sensors 205 can include apparatuses that candetect characteristics within and/or around a Host. Sensors 205 can beinternal to Host Monitoring Device 200 or external, and/or havecomponents that are partially internal and/or partially external. By wayof illustrative example, sensors can include thermometers, analytesensors (e.g., glucose sensors and/or continuous glucose monitoringsensors), health rate monitors, activity trackers, pulse oximeters,wearables (e.g., smart watches, smart rings, workout monitors,electrocardiographs, bioimpedence sensors, breathing monitors, sleepmonitors, posture monitors, habit detectors, temperature trackers,fabrics embedded with sensors, moisture detectors, etc.), medicaldevices, drug sensors (e.g., breathalyzers and sensors configured tomeasure intoxication or presence of drugs), gyroscopes, speedometers,pedometers, blood pressure readers, medical device sensors, movementsensors, respirators, and/or any sensors desirable. Data and/or commandsto/from Sensors 205 can be sent using Communicator 207.

In some implementations, Locator 206 can identify the location of HostMonitoring Device 200 and/or a Host. For example, Locator 206 caninclude GPS, Radio Frequency Identification (“RFID”), Global NavigationSatellite System (“GLONASS”), and/or any system that can identifylocation. In some implementations, Locator 206 can be positioned withina chassis of Host Monitoring Device 200. In other implementations,Locator 206 can be positioned on a Host, not within the chassis of HostMonitoring Device 200. Moreover, Locator 206 may include, or may becommunicatively coupled to, transmitters and/or receivers capable ofemitting signals that can be used to triangulate and/or otherwise derivethe position of Host Monitoring Device 200. A controller, such asController 201, can perform such algorithms to calculate location basedon emitted signals from Locator 206.

In some implementations, Communicator 207 can communicatively coupleHost Monitoring Device 200, and/or any components therein (e.g.,Operative Modules 204), to a network, computer, mobile device (e.g.,tablets, cellphones, smartphones, e-readers, phablets, and the like),short-range receiver, long-range receiver, watch, remote, antenna,wearables (e.g., smart watches, smart rings, workout monitors,electrocardiographs, bioimpedence sensors, breathing monitors, sleepmonitors, posture monitors, habit detectors, temperature trackers,fabrics embedded with sensors, moisture detectors, etc.), medicaldevices, set-top boxes, internet streaming devices, gaming consoles,smart appliances, any device with access to the internet and/or anynetwork protocol, and/or any device desirable. Communicator 207 caninclude transmitters, receivers, transceivers, etc. Communicator 207 canbe configured to send/receive over wired and/or wireless connections,such as any wired and/or wireless connection described in thisdisclosure.

Communicator 207 can be configured to send and receive signals includingnumbers, letters, alphanumeric characters, and/or symbols. In somecases, signals can be encrypted, using algorithms such as 128-bit or256-bit keys and/or other encryption algorithms complying with standardssuch as the Advanced Encryption Standard (“AES”), RSA, Data EncryptionStandard (“DES”), Triple DES, and the like. Communicator 207 can beconfigured to send and receive statuses, commands, and otherdata/information. For example, Communicator 207 can transmit statuses,commands, and/or data/information from Sensors 205, Data Storage 209,Locator 206, Communicator 207, User Interface 208, Information Manager210, Signal Processor 211, Operating Systems 213, Controller 201, PowerSupply 203, Memory 202, and/or any other component and/or subcomponentof Host Monitoring Device 200.

In some implementations, Communicator 207 can be configured to operateon a mobile ad hoc network (“MANET”). In some cases, Host MonitoringDevice 200 can be part of a distributive network where informationand/or data can be relayed, in whole or in parts) across other hostmonitoring devices, remote monitoring devices, and/or other devices.Advantageously, a MANET can allow additional robustness for the transferof important data. Because it may already be desirable to send data to aplurality of devices, using a MANET can increase signal strength,robustness, and reliability, while decreasing energy use, interference,and infrastructural costs, especially when such devices are in closeproximity of other devices. For example, such close proximity may bepredetermined by hardware limitations of Communicators 207. In someimplementations, close proximity can be based on standard ranges ofwireless standard devices, such as between 0 and 1,045 square meters orthe standard ranges (e.g., using any standard used in the art) aswireless standard devices are updated from time to time.

Data Storage 209 can be configured to temporarily and/or permanentlystore (e.g., record) data. Data Storage 209 can include storage devicesthat can store data using different mediums, such as electrical (e.g.,semiconductors, floating-gate transistors, hard disks, flash memory,RAM, ROM, enterprise storage, cloud, distributive storage devices,etc.), optical storage (e.g., photographic, microform, holographic,optical disk, magneto-optical drives, 3D optical data storage,holographic data storage), chemicals (e.g., organics, proteins,synapses, receptors, chemical concentrations, etc.), thermodynamics(e.g., phase change materials, heat storage devices, etc.),photochemicals (e.g., films, etc.), mechanical (e.g., switches),magnetic storage (e.g., magnetic tape, wire, etc.), etc. Data Storage209 can be configured to store any data desired, such as the datadescribed with respect to FIGS. 1A-B, including data from analytesensors, remote monitoring device(s), host monitoring device(s), andother device(s), communications, Contextual Data (e.g., time/amount/typeof taken medicament, such as insulin, sulfonylureas, biguanids,meglitinides, thiazolidinediones, DPP-4 inhibitors, SGLT2 inhibitors,alpha-glucosidase inhibitors, bile acid sequestrants, and/or other drugsor treatments, time/amount/type of ingested food, such as carbohydrates,protein, dairy, fat, fruits, vegetables, candy, dessert, sugars,calories, quantities, preparations, etc., time/amount/type of exerciseor activity undertaken, such as running, walking, sports, weightlifting, sitting, sleeping, idle, resting, etc., level of stress felt,such as acute, episodic acute, emotional, chronic, high stress, mediumstress, low stress, no stress, anxiety, panic attack, etc., environment,such as weather, humidity, pressure, temperature, etc. and/or location,time of day, and/or other Contextual Data), Processed Data, Health Data,System Data, Treatment Data, User Data, Sensor Data, Summary Data,and/or other Data described in this disclosure, and/or patterns and/orcombinations of any of the aforementioned. Data Storage 209 can alsostore any information based on data from any component of HostMonitoring Device 200, including Controller 201, Power Supply 203,and/or modules in Operative Modules 204. Some data can be inputted byUser Interface 208 and subsequently stored.

Data Manager 210 can be configured to analyze and/or manage data in DataStorage 209, Memory 202, and/or any component of Host Monitoring Device200 (e.g., Controller 201, Power Supply 203, and/or modules in OperativeModules 204). Operations that Data Manager 210 can use on such datainclude, but are not limited to, compression, decompression, sorting,categorizing, directing, optimizing, defragging, deleting, secureerasing, securing, manipulating, identifying, copying, pasting, writeprotecting (e.g., temporary write protection or permanent writeprotection), backing up, authenticating, etc. Advantageously, DataManager 210 can identify the types and/or severity (e.g., the importanceof) of communications by Host Monitoring Device 200. In some cases, suchidentification can allow Hosts to sort the information they receive, anddetermine the kinds and/or amounts of information that they desire tosee. Data Manager 210 can have predetermined (e.g., programmed oruser-defined) rules for allowing certain kinds and/or types ofinformation to be shown (e.g., displayed using User Interface 208) to aHost. Similarly, Data Manager 210 can also be configured to manage whatdata Host Monitoring Device 200 shares to others, such as remotemonitoring devices and other devices. Data Manager 210 can also performerror monitoring, error correction, and/or data validation, includingidentifying and/or fixing transmission-related errors, data formatting,device-related error codes, invalid data, duplicate data points, and/orother processes on the data.

User Interface 208 can be configured for a user to communicate with HostMonitoring Device 200. For example, User Interfaces 208 can includetouch panels, buttons, keypads/keyboards, ports (e.g., USB, DVI, DisplayPort, E-Sata, Firewire, PS/2, Serial, VGA, SCSI, audio port, HDMI,PCMCIA ports, memory card ports (e.g., SD and miniSD), and/or ports forcomputer-readable medium), mouse, rollerballs, consoles, vibrators,audio transducers, and/or any interface for a user to input and/orreceive data and/or commands, whether coupled wirelessly or throughwires (including, any of the wireless or wired connections described inthis disclosure). User Interface 208 can include a display, such asLCDs, LED displays, LED LCD displays, IPSs, cathode ray tubes, plasmadisplays, HD panels, 4K displays, retina displays, organic LED displays,touchscreens, surfaces, canvases, and/or any displays, televisions,monitors, panels, and/or devices known in the art for visualpresentation.

Signal Processor 211 can be configured to process any data of HostMonitoring Device 200, including, as a non-limiting example, data storedin Data Storage 209 and/or managed by Data Manager 210. Signal Processor211 can perform any analysis of data presented in this disclosure, aswell as other analyses and/or processes. By way of illustrative example,Signal Processor 211 can determine patterns in analyte measurements,such as patterns in glucose level and other data (e.g., communications,Processed Data, Contextual Data, Health Data, System Data, TreatmentData, User Data, Sensor Data, Summary Data, and/or other data mentionedin this disclosure). Advantageously, the analysis of such patterns canallow predictive communications that can assist a Host and/or RemoteMonitor(s) regarding Host care. By way of another illustrative example,Signal Processor 211 can analyze patterns in data from remote monitoringdevice(s) and/or other device(s). Where such data is based oncharacteristics (e.g., temporary or permanent) of a Remote Monitor,Signal Processor 211 can analyze patterns that can allow optimizedcommunications that can accommodate Host and/or Remote Monitorinteraction based on conditions of the Remote Monitor and/or Host.

Power Supply 203 can include one or more batteries, including, lithium,lithium ion, nickel-cadmium, nickel-metal hydride, nickel-hydrogen,carbon-zinc, silver-oxide, zinc-carbon, zinc-air, mercury oxide,alkaline, or any other type of battery known in the art. Certainbatteries can be rechargeable, such as wirelessly (e.g., by a resonantcircuit and/or a resonant tank circuit) and/or by plugging into anexternal power source. Power Supply 203 can also be any supplier ofenergy, including wall sockets and electronic devices that convertsolar, wind, water, nuclear, hydrogen, gasoline, natural gas, fossilfuels, mechanical energy, steam, and/or any power source intoelectricity.

Operating System 213 can be configured to manage Memory 202, Controller201, Power Supply 203, modules in Operative Modules 204, and/or anysoftware, hardware and/or features of Host Monitoring Device 200. Forexample, Operating System 213 can include device drivers to managehardware resources for Host Monitoring Device 200.

As previously mentioned, any of the aforementioned components of HostMonitoring Device 200 can be instantiated in software and/or hardware.For example, a module can be a piece of hardware or can be a module ofcode run on a computer.

Similarly, FIG. 3 illustrates a functional block diagram of an exampleremote monitoring device. Remote Monitoring Device 300 can includeController 301, Memory 302, Power Supply 303, and/or Operative Modules304, each of which can be operatively and/or communicatively coupled toeach other and each other's components and/or subcomponents. Controller301 can control the various operations performed by Remote MonitoringDevice 300. Like-labeled components of Remote Monitoring Device 300 canhave analogous and/or substantially similar functionality as those ofHost Monitoring Device 200, described with respect to FIG. 2. Somecomponents will be re-described here. It should be noted that, in someimplementations, host monitoring devices (e.g., Host Monitoring Device200) can also serve as remote monitoring devices (e.g., RemoteMonitoring Device 300) and vice versa. In some implementations, RemoteMonitoring Device 300 can be configured to perform the exampleprocesses, methods, and/or systems, and/or substantially similarlyprocesses, methods, and/or systems, illustrated in FIG. 1B.

Controller 301 can be operatively and/or communicatively coupled toMemory 302, which can include, volatile, non-volatile, ROM, and/or RAM,and can provide instructions and data to Controller 301. A portion ofMemory 302 can also include NVRAM. Controller 301 can perform logicaland arithmetic operations based on program instructions stored withinMemory 302. Controller 301 can include one or more processors (e.g.,microprocessors) and other peripherals. The instructions in Memory 302can be executable to implement the methods described herein. OperativeModules 304 can be coupled to Controller 301 to perform the variousoperations described in this disclosure. One or more, or none, of themodules in Operative Modules 304 can be included in someimplementations. Throughout this disclosure, reference will be made tovarious controllers and/or processors. In some implementations, a singlecontroller (e.g., Controller 301) can serve as the various controllersand/or processors described. In other implementations, differentcontrollers and/or processors can be used. Controller 301 can send andreceive signals, such as power signals, control signals, sensor signals,interrogatory signals, status signals, data signals, electrical signalsand/or any other desirable signals, including discrete and analogsignals. Controller 301 can coordinate and/or manage Operative Modules304, and/or set timings (e.g., synchronously or asynchronously), turnon/off, control power budgets, receive/send network instructions and/orupdates, update firmware, send interrogatory signals, receive and/orsend statuses, and/or perform any operations for running features ofRemote Monitoring Device 300.

Operative Modules 304 can include various modules that perform functionsfor Remote Monitoring Device 300. For example, such modules of OperativeModules 304 can include Sensors 305, Data Storage 309, Locator 306,Communicator 307, User Interface 308, Information Manager 310, and/orSignal Processor 311.

In some implementations, Sensors 305 can include apparatuses that candetect characteristics within and/or around a Remote Monitor. Sensors305 can be internal to Remote Monitoring Device 300 or external, and/orhave components that are partially internal and/or partially external.By way of illustrative example, sensors can include thermometers,analyte sensors (e.g., glucose sensors and/or continuous glucosemonitoring sensors), health rate monitors, activity trackers, pulseoximeters, wearables (e.g., smart watches, smart rings, workoutmonitors, electrocardiographs, bioimpedence sensors, breathing monitors,sleep monitors, posture monitors, habit detectors, temperature trackers,fabrics embedded with sensors, moisture detectors, etc.), medicaldevices, accelerometers, gyroscopes, speedometers, pedometers, bloodpressure readers, pump data for administration of other drugs, drugsensors (e.g., breathalyzers and sensors configured to measureintoxication or presence of drugs), movement sensors, respirators,and/or any sensors desirable. Data and/or commands to/from Sensors 305can be sent using Communication 307.

In some implementations, Locator 306 can identify the location of RemoteMonitoring Device 300 and/or a Remote Monitor who is associated withRemote Monitoring Device 300. For example, Locator 306 can include GPS,RFID, GLONASS, and/or any system that can identify location. In someimplementations, Locator 306 can be positioned within a chassis ofRemote Monitoring Device 300. In other implementations, Locator 306 canbe positioned on a Remote Monitor, not within a chassis of RemoteMonitoring Device 300. Moreover, Locator 306 can include, or becommunicatively coupled to, transmitters and/or receivers that can emitsignals that can be used to triangulate and/or otherwise derive theposition of Remote Monitoring Device 300. A controller, such asController 301, can perform such algorithms to calculate location basedon emitted signals from Locator 306.

In some implementations, Communicator 307 can communicatively coupleRemote Monitoring Device 300, and/or any components therein (e.g.,Operative Modules 304), to a network, computer, mobile device (e.g.,tablets, cellphones, smartphones, e-readers, phablets, and the like),short-range receiver, long-range receiver, watch, remote, antenna,wearables (e.g., smart watches, smart rings, workout monitors,electrocardiographs, bioimpedence sensors, breathing monitors, sleepmonitors, posture monitors, habit detectors, temperature trackers,fabrics embedded with sensors, moisture detectors, etc.), medicaldevices, set-top boxes, internet streaming devices, gaming consoles,smart appliances, any device with access to the internet and/or anynetwork protocol, computers and/or any device desirable. Communicator307 can include transmitters, receivers, transceivers, etc. Communicator307 can be configured to send/receive over wired and/or wirelessconnections, such as any wired and/or wireless connection described inthis disclosure.

Communicator 307 can be configured to send and receive signals includingnumbers, letters, alphanumeric characters, and/or symbols. In somecases, signals can be encrypted, using algorithms such as 128-bit or256-bit keys and/or other encryption algorithms complying with standardssuch as the AES, RSA, DES, Triple DES, and the like. Communicator 307can be configured to send and receive statuses, commands, and otherdata/information. For example, Communicator 307 can transmit statuses,commands, and/or data/information from Sensors 305, Data Storage 309,Locator 306, Communicator 307, User Interface 308, Information Manager310, Signal Processor 311, and/or Operating Systems 313. In someimplementations, Communicator 307 can operate on a MANET substantiallysimilar to Communicator 207.

Data Storage 309 can be configured to temporarily and/or permanentlystore (e.g., record) data. Data Storage 309 can include storage devicesthat can store data using different mediums, such as electrical (e.g.,semiconductors, floating-gate transistors, hard disks, flash memory,RAM, ROM, enterprise storage, cloud, distributive storage devices,etc.), optical storage (e.g., photographic, microform, holographic,optical disk, magneto-optical drives, 3D optical data storage,holographic data storage), chemicals (e.g., organics, proteins,synapses, receptors, chemical concentrations, etc.), thermodynamics(e.g., phase change materials, heat storage devices, etc.),photochemicals (e.g., films, etc.), mechanical (e.g., switches),magnetic storage (e.g., magnetic tape, wire, etc.), etc. Data Storage309 can be configured to store any data desired, such as the datadescribed with respect to FIGS. 1A-B and Data Storage 309.Advantageously, in certain implementations, Data Storage 309 can includedata related to a Remote Monitor associated with Remote MonitoringDevice 300 and/or other Remote Monitors. For example, data stored inData Storage 309 can include classifications (e.g., hierarchical orlateral) regarding the relative role of Remote Monitors with respect toeach other and with respect to a Host. Such data can be used by RemoteMonitoring Device 300, Host Monitoring Device 200, and/or any otherdevice to determine which remote monitoring device (e.g., which remotemonitoring device associated with which Remote Monitor) should receivedata first, second, third, etc., and which Remote Monitors are inposition to effectively and/or efficiently assist and/or otherwiseinteract with a Host.

Data Manager 310 can be configured to analyze and/or manage data in DataStorage 309, Memory 302, and/or any component of Remote MonitoringDevice 300 (e.g., Controller 301, Power Supply 303, and/or modules inOperative Modules 304). Operations that Data Manager 310 can use on suchdata include, but are not limited to, compression, decompression,sorting, categorizing, directing, optimizing, defragging, deleting,secure erasing, securing, manipulating, identifying, copying, pasting,write protecting (e.g., temporary write protection or permanent writeprotection), backing up, authenticating, etc. Advantageously, DataManager 310 can identify the types and/or severity (e.g., the importanceof) of notifications and alerts received by Remote Monitoring Device300. In some cases, such identification can allow Remote Monitors tosort the information they receive, and determine the kinds and/oramounts of information that they desire to see. Data Manager 310 canhave predetermined (e.g., programmed or user-defined) rules for allowingcertain kinds and types of information to be shown (e.g., displayedusing User Interface 308) to a Remote Monitor. Similarly, Data Manager310 can also be configured to manage what data is shared by RemoteMonitoring Device 300 to others, such as host monitoring devices andother devices. Data Manager 310 can also perform error monitoring, errorcorrection, and/or data validation, including identifying and/or fixingtransmission-related errors, data formatting, device-related errorcodes, invalid data, duplicate data points, and/or other processes onthe data.

User Interface 308 can be configured for a user (e.g., a Remote Monitorand, in some cases, a Host) to communicate with Remote Monitoring Device300. For example, User Interfaces 308 can include touch panels, buttons,keypads/keyboards, ports (e.g., USB, DVI, Display Port, E-Sata,Firewire, PS/2, Serial, VGA, SCSI, audio port, HDMI, PCMCIA ports,memory card ports (e.g., SD and miniSD), and/or ports forcomputer-readable medium), mouse, rollerballs, consoles, vibrators,audio transducers, and/or any interface for a user to input and/orreceive data and/or commands, whether coupled wirelessly and/or throughwires (including, any of the wireless and/or wired connections describedin this disclosure). User Interface 308 can include a display, such asLCDs, LED displays, LED LCD displays, IPSs, cathode ray tubes, plasmadisplays, HD panels, 4K displays, retina displays, organic LED displays,touchscreens, surfaces, canvases, and/or any displays, televisions,monitors, panels, and/or devices known in the art for visualpresentation.

Signal Processor 311 can be configured to process any data of RemoteMonitoring Device 300, including, as a non-limiting example, any datastored in Data Storage 309 and/or managed by Data Manager 310. SignalProcessor 311 can perform any analysis of data presented in thisdisclosure, as well as other analyses and/or processes. By way ofillustrative example, Signal Processor 311 can determine patterns inanalyte measurements, such as patterns in glucose level and other data(e.g., communications, Processed Data, Contextual Data, Health Data,System Data, Treatment Data, User Data, Sensor Data, Summary Data,and/or other data mentioned in this disclosure). Advantageously, theanalysis of such patterns can allow predictive notifications that canassist a Host and/or Remote Monitor(s) regarding Host care. By way ofanother illustrative example, Signal Processor 311 can analyze patternsin data and/or information from host monitoring device(s) and/or otherdevice(s). Where such data and/or information is based oncharacteristics (e.g., temporary or permanent) of a Remote Monitor,Signal Processor 311 can analyze patterns that can allow optimizedcommunications that can accommodate Host and/or Remote Monitorinteractions based on conditions and/or data of the Remote Monitorand/or Host.

Power Supply 303 can include any of the sources described with respectto Power Supply 203. Operating System 313 can be configured to manageMemory 302, Controller 301, Power Supply 303, modules in OperativeModules 304, and/or any software, hardware and/or features of RemoteMonitoring Device 300. For example, Operating System 313 can includedevice drivers to manage hardware resources for Host Monitoring Device300.

As previously mentioned, any of the aforementioned components of RemoteMonitoring Device 300 can be instantiated in software and/or hardware.For example, a module can be a piece of hardware or can be a module ofcode run on a computer.

FIG. 4 illustrates a diagram of an example host monitoring devicecommunicatively coupled to remote monitoring devices. Monitoring System400 can include Host Monitoring Device 402 and Remote Monitoring Device404. For example, Host Monitoring Device 402 can be configuredsubstantially similar to Host Monitoring Device 200 and/or performprocesses substantially similar to Process 100. Similarly, RemoteMonitoring Device 404 can be configured substantially similar to RemoteMonitoring Device 300 and/or perform processes substantially similar toProcess 150. In some implementations, Host Monitoring Device 402 can becommunicatively coupled to Remote Monitoring Device 404. Host MonitoringDevice 402 can be associated with a Host, and Remote Monitoring Device404 can be associated with a Remote Monitor. Host Monitoring Device 402and Remote Monitoring Device 404 can be configured to send and receivecommunications (e.g., messages, notifications, alerts, interrogativesignals, status signals, synchronization signals, timer signals, data,information, etc.) from each other.

In some implementations, Monitoring System 400 can also include RemoteMonitoring Device 406, which can also be configured substantiallysimilar to Remote Monitoring Device 300 and/or perform processessubstantially similar to Process 150. Remote Monitoring Device 406 canbe communicatively coupled to both Host Monitoring Device 402 and RemoteMonitoring Device 404, where Host Monitoring Device 402 and RemoteMonitoring Devices 404, 406 can be configured to send and/or receivecommunications (e.g., messages, notifications, alerts, interrogativesignals, status signals, synchronization signals, timer signals, data,information, etc.) from each other.

FIG. 5 illustrates an example extended system having a plurality of hostmonitoring devices and remote monitoring devices communicatively coupledthrough a network. Monitoring System 500 can include one or more of HostMonitoring Devices 502A-N, Remote Monitoring Devices 508A-N, and/orNetwork(s) 510. For example, Host Monitoring Devices 502A can beconfigured substantially similar to Host Monitoring Device 200 and/orperform processes substantially similar to Process 100. Similarly,Remote Monitoring Device 508A-N can be configured substantially similarto Remote Monitoring Device 300 and/or perform processes substantiallysimilar to Process 150.

In some example implementations, Remote Monitoring Device 508A canreceive communications for a single host monitoring system, such as HostMonitoring Device 502A, or a plurality of host monitoring systems, suchas Host Monitoring Systems 502A-N. Furthermore, data can be generated bySecure Server 504 and then be sent to the one or more of RemoteMonitoring Devices 508A-N and/or Host Monitoring Devices 502A-N. SecureServer 504 can be a server that can be configured to perform Processes100, 150, and/or other processes.

In some implementations, Network(s) 510 can include a collection ofhardware, software, services, and/or resources that can be invoked toinstantiate a virtual machine, process, or other resource for a limitedor defined duration, or an unlimited or undefined duration. Network(s)510 can be communicatively or operatively coupled to a plurality ofdevices, systems, and/or servers, including devices and servers. In someimplementations, Network(s) can include systems such as notificationservice, Short Message Service (“SMS”), wireless personal area networks(“WPANs”), wireless local area network (“WLAN”), wireless mesh networks,wireless metropolitan area networks, wireless wide area networks, globalarea networks, space networks, cellular networks (e.g., 2G, 4G, LongTerm Evolution (“LTE”), 5G), mobile networks, local area network(“LAN”), star networks, ring networks, bus networks, and/or any othernetwork. Network(s) 510 can include Secure Server 504 and Workstation506.

In some implementations, there can be situations where it is desirabletemporarily or permanently to coordinate care for Hosts. For example,Caretakers can be temporarily taking care of a plurality of Hosts inclose proximity, and the care of one or more Host can be aided by datafrom other Hosts. In some cases, a plurality of host monitoring devices(e.g., Host Monitoring Devices 502A-N) can be in the same monitoringsystem and/or communicate with one another. For example, a hostmonitoring device, remote monitoring device, and/or secure server cantake into account the location of other host monitoring devices inproximity to a particular host monitoring device. Such other hostmonitoring devices can be used to gather more information that couldprovide context to a particular host monitoring device. By way ofillustrative example, in the case where Host Monitoring Device 502A andHost Monitoring Device 502B are in the vicinity (e.g., within 20 metersor any determined area) of each other. Host Monitoring Device 502A maynot indicate that its Host is eating, but Host Monitoring Device 502Bmay show that its Host is eating. Host Monitoring Device 502B can send acommunication to Host Monitoring Device 502A, Secure Server 504, and/orRemote Monitoring Devices 508A-N. In this scenario Host MonitoringDevice 502A, Secure Server 504, and/or Remote Monitoring Devices 508A-Ncould find that there is an increased likelihood that the Host of HostMonitoring Device 502A is going to eat and/or can be impacted by aphysical response due to the smell and/or sight of food, which couldincrease insulin levels and/or lower glucose levels of the Host of HostMonitoring Device 502A. Host Monitoring Device 502A can receive databased on the communication from Host Monitoring Device 502B. In someimplementations, Host Monitoring Device 502A can then sendcommunications (e.g., to Host Monitoring Devices 502B-N, RemoteMonitoring Devices 508A-N, and/or Secure Server 504) indicating thatthere could be an event such as lowered glucose levels. In someimplementations, Host Monitoring Device may, instead or in addition,enter data into a log indicating that Host Monitoring Device 502Bindicated its Host was eating in the vicinity of Host Monitoring Device502A.

One or more Remote Monitors can monitor the health of a plurality ofHosts. In an illustrative example, one or a few nurses in a school or aschool district may be in charge of monitoring health and well-being ofhundreds or thousands of students, where a percentage of the studentsmay be diabetic patients. In some embodiments, a school nurse can beRemote Monitor and can remotely monitor multiple diabetic students froma remote monitoring device. This can also allow ease and speed ofcommunication between the school nurse and teachers of diabeticstudents. The locator feature of host remote monitoring devices ofdiabetic students can allow the school nurse, teachers or schooladministrators to timely find an unresponsive child on school premisesor during field trips. In some embodiments, the student patient (studentHost(s)) can use a dedicated host monitoring device at school and leavethe device at school outside school hours. The dedicated host monitoringdevice can pair with the student Host's transmitter when the student isat school and in range. The school nurse's remote monitoring device canmonitor the student Host's sensor and other data as described hereinwith respect to Remote Monitor. Once school is over, the student Hostpatient can leave the dedicated school device in classroom or on schoolpremises. Once the student Host arrives at home, and is in range with aremote monitoring device typically used by Remote Monitor(s) in the homesuch as the student Host's parents, the student Host's transmitter canthen pair with such home remote monitoring devices. In some embodiments,the student Host's transmitter can be configured to be allowed to linkto multiple devices.

In some embodiments, the classifications associated with a studentHost's Remote Monitor(s) can be altered based on detecting the studentHost's location and/or time of day. For example, upon detection that thestudent Host is at school, the school nurse remote monitoring device canbe elevated to a higher priority classification and other remotemonitoring devices, such as those in the student Host's home, can berelegated to a lower priority classification. Conversely, upon detectingthat the student Host is at home, the remote monitoring device of theschool nurse can be relegated to a lower priority classification andother the Remote Monitor(s), e.g., including the Remote Monitor(s) ofthe student Host's home, can be elevated to a higher priorityclassification. In some embodiments, one or more remote monitors mayenjoy a permanent classification as to never miss any alarms ornotifications.

As described, a school nurse could have a plurality of students withhost monitoring devices that he/she is monitoring, e.g., as a RemoteMonitor. For example, a first student could have Host Monitoring Device502A and a second student could have Host Monitoring Device 502B.Information gathered from Host Monitoring Device 502B could have animpact on the health of the first student with Host Monitoring Device502A. For example, emotional stress of the second student with HostMonitoring Device 502B could be measured using any device described inthis disclosure, such as a heart rate monitor, smart watch, bloodpressure monitor, etc. That measured data could be used as ActionableData for the first student, where the stress of the second student couldbe indicative that the stress of the first student will increase.Accordingly, Host Monitoring Device 502B can send communicationsindicative of the emotional stress of the second student to one or moreof Host Monitoring Device 502A, Secure Server 504, and/or RemoteMonitoring Devices 508A-N. Host Monitoring Device 502A can receive databased on the communication from Host Monitoring Device 502B. In someimplementations, Host Monitoring Device 502A can then sendcommunications (e.g., to Host Monitoring Devices 502B-N, RemoteMonitoring Devices 508A-N, and/or Secure Server 504) indicating that itsHost could be under stress. In some implementations, Host MonitoringDevice may, instead or in addition, enter data into a log indicatingthat Host Monitoring Device 502B indicated its Host was stressed in thevicinity of Host Monitoring Device 502A. For example, such contextualdata sharing can empower the first student to positively intervene onbehalf of the second student exhibiting the increased stress, as well asbe self-aware on how the second student's emotional condition mightaffect him/herself. Also, for example, the contextual data benefits theschool nurse to be aware and vigilant for how the stress situation ofthe second student might affect the other Hosts that he/she is remotelymonitoring.

Embodiments described herein may be used to create a support oreducation community of patients and health care providers. DisposableCGMs can be provided to diabetic patients in community events, forexample, a diabetes camp, where health care professionals can educatethe interested members of the public and their loved ones on theavailable technologies described herein and offer a hands-on chance forreviewing the benefits thereof.

As another non-limiting example, in some cases the Host having HostMonitoring Device 502A may not have other devices that can measure datathat can put that Host's analyte measurements into context (e.g.,Processed Data, Contextual Data, Health Data, System Data, TreatmentData, User Data, Sensor Data, Summary Data, and/or other data mentionedin this disclosure). In some cases, Host Monitoring Device 502A cancollect data from other host monitoring devices in its proximity toobtain such data. For example, the Host of Host Monitoring Device 502Ahas no other devices and the Host of Host Monitoring Device 502B has oneor more other devices, such as a thermometer that can measure ambienttemperature. Host Monitoring Device 502B can send communicationsindicative of the data measured by the thermometer to Host MonitoringDevice 502A, Secure Server 504, and/or Remote Monitoring Devices 508A-N.Host Monitoring Device 502A can receive data based on the communicationsfrom Host Monitoring Device 502B. In some implementations, HostMonitoring Device 502A can then send communications (e.g., to HostMonitoring Devices 502B-N, Remote Monitoring Devices 508A-N, and/orSecure Server 504) indicating the temperature of the environment of theHost. In some implementations, Host Monitoring Device may, instead or inaddition, enter data into a log indicating the temperature measured byHost Monitoring Device 502B in the vicinity of Host Monitoring Device502A. In this illustrative example, a remote monitoring device (e.g.,Remote Monitoring Device 508A-N) in the proximity of Host MonitoringDevice 502A can be used instead or in addition to Host Monitoring Device502B.

As another non-limiting example, where a Host associated with a firsthost monitoring device needs assistance, and his/her Remote Monitors arenot available or responsive, having the ability to communicate with asecond host monitoring device in the vicinity can give a greaterlikelihood of assistance because the Host associated with the secondhost monitoring device could be a diabetic with similar experiences.Accordingly, Host Monitoring Devices 502A-N can be operatively coupledto each other directly and/or through Network(s) 510.

In some implementations, Workstation 506 can be an access point such asdevices, systems, and/or servers, including, but not limited to,computers, mobile devices, tablets, smart phones, cell phones, personaldigital assistants, phablets, e-readers, smart watches, set-top boxes,internet streaming devices, gaming consoles, smart appliances, and/orany device with access to the internet and/or any network protocol.Workstation 506 can be used to access, read, generate, write, receive,and/or otherwise manipulate data and/or information accessible throughNetwork(s) 510. Workstation 506 also can be used to perform systemmaintenance, updates, and/or optimizations.

Secure Server 504 can be a depository and/or processor of data from HostMonitoring Devices 502A-N, Remote Monitoring Devices 508A-N, Workstation506, other devices (e.g., mobile devices (e.g., tablets, cellphones,smartphones, e-readers, phablets, and the like), wearables (e.g., smartwatches, smart rings, workout monitors, electrocardiographs,bioimpedence sensors, breathing monitors, sleep monitors, posturemonitors, habit detectors, temperature trackers, fabrics embedded withsensors, moisture detectors, etc.), set-top boxes, internet streamingdevices, gaming consoles, smart appliances, any device with access tothe internet and/or any network protocol, computers (e.g., laptops,desktops, personal computers, etc.), medical devices, heart ratemonitors, activity trackers, pulse oximeters, accelerometers,gyroscopes, speedometers, pedometers, blood pressure readers, pump datafor administration of other drugs, drug sensors (e.g., breathalyzers andsensors configured to measure intoxication or presence of drugs),continuous glucose monitors, and/or any desirable device), and/or anysystem connected to Network(s) 510 and/or Secure Server 504. SecureServer 504 can perform any function and/or operation that could beperformed by host monitoring devices or remote monitoring devices (e.g.,Process 100, Process 150, and/or any other method or process describedin this disclosure), as well as other functions and operations.Likewise, any functionality herein ascribed to Secure Server 504 canalso be performed by a host monitoring device or remote monitoringdevice. In some implementations Secure Server 504 can be software and/orhardware that requests and/or receives data from other devices orsoftware. Secure Server 504 can include modules and/or other servers,including database servers, file servers, mail servers, print servers,web servers, application servers, etc. For example, Secure Server 504can perform functions and/or operations substantially similar to DataStorages 209, 309, Data Managers 210, 310, Signal Processors 210, 310,and/or components of Operative Modules 204, 304. Secure Server 504 canalso be communicatively and/or operatively coupled to any operativemodules described in this disclosure, including, but not limited to,operative modules substantially similar to Operative Modules 204, 304,such as modules substantially similar to Locators 206, 306, Coordinators212, 312, User Interfaces 208, 308, Communicators 207, 307, Sensors 205,205, etc. Also, any of the functions and/or operations described withrespect to Secure Server 504 can be performed by Data Storages 209, 309,Data Manager 210, 310, Signal Processors 210, 310, and/or components ofOperative Modules 204, 304. In some implementations, Secure Server 504can be replaced, and/or its functionality performed by, any otherserver, including an unsecure server.

In some implementations, Secure Server 504 can also provide acloud-based data management framework that receives patient-related datafrom various devices, such as a medical device, a glucose meter, acontinuous glucose monitor, a sensor system, a receiver, and/or otherdevices (e.g., a device providing food consumption, such ascarbohydrates, consumed by a host or Remote Monitor, medicament deliverydata, time of day, temperature sensors, exercise/activity sensors, andthe like), including any device described in this disclosure.Furthermore, in some implementations, the cloud-based data managementsystem can receive data programmatically with little (or no)intervention on the part of a user. The data received from devices,receivers, source systems, and the like can be in a variety of formatsand can be structured or unstructured. For example, Secure Server 504can receive raw sensor data from sensors (e.g., Sensors 205, 305, andsensors of other devices), which has been minimally processed oranalyzed, and the received data can then be formatted, processed (e.g.,analyzed), and/or stored in order to enable report generation by SecureServer 504. In addition to sensor data, the Secure Server 504 can alsoreceive data from source systems, such as health care managementsystems, patient management systems, prescription management systems,electronic medical record systems, personal health record systems, andthe like. Secure Server 504 can also receive any data described in thisdisclosure (e.g., analyte measurements, communications, Processed Data,Contextual Data, Health Data, System Data, Treatment Data, User Data,Sensor Data, Summary Data, and/or other data mentioned in thisdisclosure).

In some example implementations, Secure Server 504 can check receiveddata for transmission-related errors, data formatting, device-relatederror codes, validity of the data, duplicate data points, and/or otheraspects of the data. Moreover, if out-of-range data points or deviceerrors are found, Secure Server 504 can identify those data points by,for example, flagging those data points, subsequently correcting theidentified data points programmatically or by a system administrator,and storing the corrected data points. Moreover, Secure Server 504 canbe configured by a user, such as a clinician, doctor, and the like, toperform additional data processing steps, such as correcting time ofday, correcting the date, and/or analyzing data by specific cohorts,groups, and relationships (e.g., demographics, such as age, city, state,gender, ethnicity, Type I diabetes, Type II diabetes, age of diabetesdiagnosis, lab results, prescription drugs being used, self-reportedconditions of a patient (e.g., Host or Remote Monitor), diagnosedconditions of a patient (e.g., Host or Remote Monitor), responses toquestions posed to a patient (e.g., Host or Remote Monitor), and/or anymetadata representative of a patient (e.g., Host or Remote Monitor).Once Secure Server 504 performs initial data processing (e.g., checks,cleaning, and analysis), the processed and/or raw data can be stored ata repository operatively and/or communicatively coupled to the SecureServer 504, and/or stored within Secure Server 504 itself.

The processing at Secure Server 504 can also include associatingmetadata with the data received from the devices (e.g., Host MonitoringDevices 502A-N, Remote Monitoring Devices 508A-N, other devices, and/orany device disclosed in this disclosure), and/or sensors (e.g., Sensors205, 305). Examples of metadata include patient information, keys usedto encrypt the data, patient accelerometer data, location data (e.g.,location of patient or location of patient's clinic), time of day, date,type of device used to generate associated sensor data, and the like.The patient information can include the patient's age, weight, sex, homeaddress and/or any past health-related information, such as whether thepatient has been diagnosed as a Type I or Type II diabetic, high-bloodpressure, and/or as having any health condition. Secure Server 504 caninclude encryption of data. For example, Secure Server can usealgorithms such as 128-bit or 256-bit keys and/or other encryptionalgorithms complying with standards such as the AES, RSA, DES, TripleDES, and the like.

The processing of Secure Server 504 can also include one or more of thefollowing: analysis, such as determining one or more descriptivemeasurements; detecting or predicting events (e.g., a hypoglycemic, ahyperglycemic, and/or any other feature detected in the sensor data);applying pattern detectors to the received sensor data; and, generatingreports based on received data. The descriptive measurements may includestatistics (e.g., median, inner, and outer quartile ranges, mean, sum,standard deviation, and coefficients of variation). In some exampleimplementations, Secure Server 504 can also associate metadata with thedata received from the devices, sensors, source system, and/orreceivers; determine one or more descriptive measurements, such asstatistics (e.g., median, inner and outer quartile ranges, mean, sum, n,and standard deviation); generate reports including descriptivemeasurements; validate and/or verify the integrity of the received datafrom the devices, sensors, source system, and/or receivers; processreceived data based on metadata (e.g., to select certain patients,devices, conditions, diabetic types, and the like); and/or correlatereceived data from the devices, sensors, source system, and/or receiversso that the data can be compared and combined for processing includinganalysis. Moreover, the results of any processing performed by SecureServer 504 can be used to generate one or more reports, such as graphs,bar graphs, static charts, charts, and the like. Furthermore, thereports and other outputs generated by Secure Server 504 can be providedto Host Monitoring Devices 502A-N, Remote Monitoring Devices 508A-N,Workstation 506, any other device described in this disclosure, and/orany system connected to Network(s) 510 and/or Secure Server 504.

Secure Server 504 can be considered secure in the sense that it can keepprivate, patient identifiable information and/or restricts access tousers registered and thus authorized to use Secure Server 504. Forexample, and without limitation Secure Server 504 can receive a requestfrom a device (e.g., Host Monitoring Devices 502A-N, Remote MonitoringDevices 508A-N, Workstation 506, any other device described in thisdisclosure, and/or any system connected to Network(s) 510 and/or SecureServer 504) to perform an action (e.g., provide data, store data,analyze/process data, request a report, request configurationinformation, request registration, and the like). Before Secure Server504 services the request, Secure Server 504 can process the request todetermine whether the request is authorized and authenticated. Forexample, an authenticator and authorizer can determine whether a senderof a request is authorized by having a user provide a securitycredential (e.g., a user identifier, a password, a stored securitytoken, and/or a verification identifier provided by text message, phone,or email) at a user interface presented on a device (e.g., HostMonitoring Devices 502A-N, Remote Monitoring Devices 508A-N, Workstation506, any other device described in this disclosure, and/or any systemconnected to Network(s) 510 and/or Secure Server 504). Secure Server 504can also consider the classification of the requester, if applicable. Ifauthorized, authenticator and authorizer can authenticate the sender ofthe request to check whether a security credential associated with thesender of the request indicates that the sender is indeed permitted toaccess a specific resource at Secure Server 504 in order to perform theaction, such as store (or upload) data at a repository, performanalyze/process data, request report generation, receive alerts, receivecommunications, and the like.

In some example implementations, Secure Server 504 can include a patterndetector to perform pattern detection on data, such as sensor datarepresentative of glucose data, analytes, and/or other data (e.g.,insulin pump data, carbohydrate consumption data, and the like). Thepattern detector can detect the pattern and/or generate an output, whichcan be provided to a report generator at Secure Server 504 forgenerating a communication and/or display page to Host MonitoringDevices 502A-N, Remote Monitoring Devices 508A-N, Workstation 506, anyother device described in this disclosure, and/or any system connectedto Network(s) 510 and/or Secure Server 504.

Moreover, the pattern detector may detect patterns in dataretrospectively for a predetermined time defined by Monitoring System500 and/or a user. For example, the pattern detector can receive inputdata from a repository coupled to Secure Server 504, and the input datacan include Sensor Data indicative of glucose concentration data,analytes, and/or other data (e.g., insulin pump data, carbohydrateconsumption data, histograms and/or counts, data from a continuousglucose monitor (CGM data), time of day, amount of carbohydrates, otherfood related information, exercise, awake/sleep timer intervals,medications ingested, and the like). Moreover, the input data caninclude historical data obtained over a timeframe, such as 8 hours, 1day, 2 days, 7 days, 30 days, and/or any other time period. For example,the input data may include counts representative of monitored analytedetection levels (e.g., glucose concentration levels) received and/orstored at Monitoring System 500 over a period covering a four-weektimeframe.

To further illustrate the pattern detector, patterns can be recognizedbased on one or more predefined triggers (also referred to as criteria,rules, and filters). Furthermore, the one or more predefined triggersmay be variable and adjustable based user input and/or programmaticallybased on one or more rules at Secure Server 504. And, some types ofpatterns may be selected, turned off and/or on, and/or modified by auser, a user's physician, and/or a user's guardian, although MonitoringSystem 500 can select, adjust, and/or otherwise modify triggersprogrammatically as well.

Some non-limiting examples of the types of relationships in the inputdata that can be considered a pattern are one or more of the following:a glucose level that exceeds a target glucose range (which may bedefined by a user, a health care provider, Secure Server 504, HostMonitoring Devices 502A-N, Remote Monitoring Devices 508A-N, any devicedescribed in this disclosure, and/or a combination thereof); a glucoselevel that is below a target glucose range; a rapid change in glucoselevel from a low to a high (or vice versa); times of day when a low, ahigh, an at range, or rapid glucose level event occurs; days when a low,a high, an at range, and/or a rapid glucose level event occurs; ahyperglycemic pattern; a hypoglycemic pattern; patterns associated witha time of day or week; a weighted scoring for different patterns basedon frequency, a sequence, and a severity; a custom sensitivity of auser; a transition from a hypoglycemic to hyperglycemic pattern; anamount of time spent in a severe event; a combination of glucose changeand time information; and/or a pattern of high variability of glucosedata. Such pattern recognition can be performed on any data described inthis disclosure (e.g., analyte measurements, communications, ProcessedData, Contextual Data, Health Data, System Data, Treatment Data, UserData, Sensor Data, Summary Data, and/or other data mentioned in thisdisclosure). Advantageously, more data types can provide context andfurther information on the health condition of the Host, as well as theHost's glucose level. Further, a pattern may be based on a combinationof previous pattern data and a currently detected situation, whereby thecombined information generates a predictive alert.

Hypoglycemic patterns by time of day may be detected based on eventsdetected by Secure Server 504. For example, a pattern can be identifiedin situations where the user has low glucose concentrations around thesame time in the day. Another type of pattern, which may be identified,is a “rebound high” situation. For example, a rebound high may bedefined as a situation where a user overcorrects a hypoglycemic event byoverly increasing glucose intake, thereby going into a hyperglycemicevent. These events can be detected based on one or more predefinedtriggers.

To further illustrate examples of the patterns, basic patterns can beconfigured to allow a search for certain patterns in the data, such asvalues within range, high coefficient of variance, and the like. Eachpattern can have one dimension, such as within range, with a separatepattern looking specifically for below range, another looking for lowcoefficient of variance, and the like. Each pattern can be statisticallybased and/or use standard descriptive statistics in the application ofpattern matching. Each pattern can be assigned scores for various rulesencoded with each pattern, such as is it positive, negative, howimportant an insight is, and the like. Each pattern can also be assigneda possible set of date ranges for which the pattern is applicable. Forexample, counting the number of times a high glucose value is followedby a low below range is a pattern that just applies to the full range.However, looking at high levels of variance can apply to a month, aweek, a day, an intraday, every other hour, hourly, and combinationsthereof. Each pattern can be assigned a minimally acceptable scorebefore it can be considered for display or generation of an alert and/ornotification message sent to one or more of Host Monitoring Devices502A-N and/or Remote Monitoring Devices 508A-N. Each pattern (and anyassociated triggers/rules) may be processed for a set of data for acertain timeframe, and if the pattern is applied and meets certainminimal requirements, then the patterns are ranked according tosignificance. As such, the ranked patterns can each correspond to analert and/or notification message sent to one or more of Host MonitoringDevices 502A-N and/or Remote Monitoring Devices 508A-N.

Connections can be established between one or more Remote MonitoringDevices 508A-N, either directly or through Network(s) 510, to provideadditional layers of oversight into the operations of Host MonitoringDevices 502A-N and/or the care of Hosts associated with Host MonitoringDevices 502A-N. The connections to Remote Monitoring Devices 508A-N canbe established based on invitations sent to Remote Monitoring Device508A-N. These invitations can be sent with the consent of the respectiveHost Monitoring Devices 502A-N to be monitored and/or their associatedHost. For example, Host Monitoring Device 502A and/or Remote MonitoringDevice 508A can be requested to both accept invitations or to enter acode (e.g., a password, shared secret, and the like) in order to optinto Remote Monitoring System 500.

In some implementations, there can be various ways to send data and/orcommunications between Secure Server 504 and Remote Monitoring Devices508A-N, Host Monitoring Devices 502A-N, and/or other devices. By way ofillustrative example, Secure Server 504 can ping Remote MonitoringDevice 508A (or any other Remote Monitoring Device 508B-N or HostMonitoring Device 502A-N) periodically (e.g., every 0.5, 1, 2, 3, 4, 5,10, 15, 30, 45 and/or 60 minutes, or at any interval desirable,including any time between the aforementioned minutes). In someimplementations, such as when Remote Monitoring Device 508A is a mobiledevice that runs a mobile application to monitor a Host, when the mobileapplication is open, it can request data (e.g., EGV data and/or any datadescribed in this disclosure) from the server following the ping.However, when the mobile application is closed, it might not receive itin some cases. In such cases, there could be additional delays inreceiving information, and/or information may not even be received, whenthe mobile application is later opened. To address such a situation,and/or where it is desirable, Secure Server 504 can send data (e.g., EGVdata and/or any data described in this disclosure) in and/or with eachping. In this manner, whether Remote Monitoring Device 508A is asleep(e.g., idle) or awake (e.g., active), it can still receive current data.

In some implementations, Remote Monitoring Devices 508A-N, HostMonitoring Devices 502A-N, and/or other devices can receive real-timeevent information as a stream. In such cases, Remote Monitoring Devices508A-N, Host Monitoring Devices 502A-N, and/or other devices can includea streaming component that can continuously or substantiallycontinuously receive data regarding a Host.

In some implementations, the data generated by Secure Server 504 can berelated to a page to be displayed at a user interface of Host MonitoringDevice 502A-N and/or Remote Monitoring Device 508A-N. This page caninclude textual and/or a graphical indication of the status of the oneor more Hosts being monitored, and/or textual and/or a graphicalindication of the status of one or more Remote Monitors following aHost. Secure Server 504 can send the actual page that can be displayed,and/or send data for one or more of Host Monitoring Device 502A-N and/orRemote Monitoring Device 508A-N to generate such a page.

By way of illustrative example, a school nurse can have RemoteMonitoring Device 508A, which can display a page depicting each of HostMonitoring Devices 502A-N that Remote Monitor 508A is monitoring. EachHost Monitoring Device 502A-N can be associated with a particular Hoststudent who is associated with that host monitoring device. FIG. 6illustrates an example page that can be displayed on a remote monitoringdevice in this example scenario. Page 600 can be displayed on RemoteMonitoring Device 508A, which can be a smart phone and/or any remotemonitoring device described in this disclosure. Page 600 can have thestatus information for each of the monitored students (e.g., GlucoseLevel 612A-C), the most recent notification message from each of themonitored students (e.g., Message 614A-C), an indication that themonitored student is within limits (e.g., Graphical Indication 610A,C),and/or an indication that the monitored student is not within limits(e.g., Graphical Indication 610B), and the like. For example, eachstudent can be associated with a cell (e.g., a defined space on thepage), such as Cells 602A-C. As such, the nurse can quickly view theuser interface and see the status of each of the students beingmonitored. Graphical Indications 610A-C can be used to visually conveythe overall status of each student in each student's cell. For example,a so-called “smiley” face icon can indicate the student's glucose levels(e.g., EGV) are within limits and a so-called “sad” face icon canindicate that student's glucose levels are of concern because they areabove a threshold. Moreover, in some example implementations, Page 600can be presented on a display (e.g., any display discussed in thisdisclosure), so that a selection using a user interface (e.g., any userinterface described in this disclosure) of a cell, text, or graphicalindication can result in additional information being displayed and/orprovided to Remote Monitoring Device 508A. Although the previous examplerefers to glucose levels (e.g., EGV) and specific types of events,communications, and graphics, other types of events, communications,and/or graphics discussed herein may be used to convey the status of aHost.

In some implementations, selecting a cell of a monitored student (e.g.,Cells 602A-C) can cause the Remote Monitoring Device 508A to access theSecure Server 504 and then receive additional data, such as one or moreof current and prior glucose levels, patient information, and the like,and update the display page or transition to a new display page thatdisplays information about the selected student in more detail (e.g.,displaying a trend graph of the student's glucose level over the pastthree hours). Such data can also be stored locally on Remote MonitoringDevice 508A. As another illustrative example, Page 600 can also bestored in memory on a server (e.g., Secure Server 504) and/or displayedon a display communicatively and/or operatively coupled to that server.

As a non-limiting example, FIG. 7A illustrates an example displayshowing additional data. When Cell 602A is selected, Page 700 can appearon Remote Monitoring Device 508A. In some cases, Page 700 can also bestored in memory on a server (e.g., Secure Server 504) and/or displayedon a display communicatively and/or operatively coupled to that server.

In some implementations, Page 700 can display Glucose Display 706 forHost 702. An image (e.g., picture, emoji, graphical representation,avatar, etc.) of Person 702 can appear as Image 704. Time Bar 710 canillustrate, and allow selection of, different windows of time fordisplay in Display 714, which can display different points ofmeasurements at different points in time (e.g., historical data) such asGlucose Measurements 715, 716. Display 714 can have axes that chartrelevant information. For example, the y-axis can be glucose levels(e.g., EGV) in mg/dL, or other units, and the x-axis can be time. Inthis way, Display 714 can display historical data of a Host over time.Selected points in Display 714 can be displayed as Glucose Display 706.For example, Glucose Measurement 715 is displayed as illustrated inGlucose Display 706. Button 708, and similar buttons for navigation, canbe used to display in Glucose Display 706 different points in Display714. By hitting Button 708, later points can be displayed. By way ofnon-limiting example, each time Button 708 is hit, Glucose Display 706can display the next glucose measurement in time (e.g., to the right).If Glucose Display 706 displays Glucose Measurement 715, pushing and/orholding a number of times (e.g., 1, 2, 3, 5, 11, and/or any otherdefined number) Button 708 can cause Glucose Display 706 to displayGlucose Measurement 716. In some cases, the current glucose level can bedisplayed in Glucose Display 706.

Thresholds can be used for communications, in which the thresholds canbe used to identify glucose measurements that when above or below thosethreshold, cause alerts, notifications, messages and/or othercommunications to be sent to one or more remote monitoring devices orother devices. These thresholds can be user configured orauto-populated, and typically coincide with the upper and lower bound ofnormal glucose levels. As a non-limiting example, Upper Threshold 718can be a predetermined threshold, in which when glucose measurements(e.g., Glucose Measurement 716) fall above Upper Threshold 718, the Hostfor which those glucose measurements corresponds may have high glucose(e.g., hyperglycemia). In such a case, an alert, notification, message,and/or other communications can be sent to remote monitoring devices(e.g., Remote Monitoring Devices 508A-N), and/or displayed informationon pages (e.g., Page 600) can be changed/updated (e.g., changingGraphical Indication 610A from a smiley face to a sad face). LowerThreshold 720 can be a predetermined threshold, in which when glucosemeasurements fall below Lower Threshold 720, the Host for which thoseglucose measurements corresponds may have low glucose (e.g.,hypoglycemia). In such a case, an alert, notification, and/or othercommunications can be sent to remote monitoring devices (e.g., RemoteMonitoring Devices 508A-N), and displayed information on pages (e.g.,Page 600) can be changed/updated (e.g., changing Graphical Indication610A from a smiley face to a sad face).

In some example implementations, pages (e.g., Page 600) can beconfigured as a so-called “dashboard” including dynamic content. Forexample, the icons for Hosts desiring the greatest care or attention(e.g., the Hosts with glycemic levels that are extremely high or low)can be arrange in the top row of page to allow the remote monitor toquickly ascertain the state of riskier Hosts. Although the previousarrangement described using the top row of the page to segregate some ofthe so-called riskier Host patients other segregation schemes can beused (e.g., different colors, intensities, and/or locations on thepage). Furthermore, pages can be considered dynamic as Hosts desiringextra attention can change over time causing the page to depictdifferent icons for different Hosts in the top row of the page, and/orany other indication. In some cases, some Hosts can be anonymous to someviewers (e.g., Hosts or Remote Monitors), where some or all of theidentifying information of a Remote Monitor (e.g., name, serial number,etc.) can be not listed.

In some implementations, Remote Monitoring Device 508A-N can receivecommunications from Host Monitoring Device 502A-N. Such communicationscan, in addition to or in the alternative, be received and/or stored onSecure Server 504. FIGS. 7B-C illustrate example communications. ExampleCommunication 722 can be presented on example Remote Monitoring Device720, which can be substantially similar to any remote monitoring devicedescribed in this disclosure (e.g., Remote Monitoring Device 300). Insome cases, Communication 722 can be received by a server (e.g., aserver substantially similar to Secure Server 504), where Communication722 is stored in memory on the server and/or displayed on a displayoperatively and/or communicatively coupled to the server. In someimplementations, Remote Monitoring Device 720 and/or the server caninclude a touch screen as a user interface, where the touch screen isconfigured to display communications and graphics, and also configuredto receive user (e.g., a Remote Monitor) inputs (e.g., responses).Notification 722 can appear as a window for user interaction when RemoteMonitoring Device 720 and/or a server receive Notification 722. Forexample, a user interaction can include a Remote Monitor pressing abutton on Remote Monitoring Device 300, touching the screen of RemoteMonitoring Device 300 over an area associated with a portion ofNotification 722, and/or activating (e.g., executing, opening, and thelike) an application (e.g., program, mobile application, graphical userinterface, user interface, etc.) at Remote Monitoring Device 720. Insome implementations, Notification 722 can appear when anotherapplication (e.g., program, mobile application, graphical userinterface, user interface, etc.) at Remote Monitoring Device 720 isactively being used. In such a scenario, Notification 722 can appear asa pop-up, tray symbol, audible signal, visual signal (e.g., light flash,turned-on light, brightened screen, etc.), vibration, and/or any otherway of indicating that a notification has been received. There, a userinteraction and/or response can include touching the screen over thearea associated with a portion of Notification 722 to acknowledgereceipt of Notification 722 before the user is allowed to resume theother application, although the user action can also preempt the otherapplication and make the remote monitoring application the activeapplication being viewed at Remote Monitoring Device 720. Moreover, thedecision of whether to preempt the other application and/or resume theother application can be predetermined based on the severity level ofthe event, so that relatively more severe events can preempt the otherapplication, while less severe events may not. In some implementations,Notification 722 can include time and/or location stamps for the Host,and/or time and/or location stamps for Remote Monitors.

FIG. 7C illustrates an example notification that may not request userinteraction. Notification 732 can be presented on example RemoteMonitoring Device 730, which can be substantially similar to any remotemonitoring device described in this disclosure (e.g., Remote MonitoringDevice 300). In some cases, Communication 732 can be received by aserver (e.g., a server substantially similar to Secure Server 504),where Communication 732 is stored in memory on the server and/ordisplayed on a display operatively and/or communicatively coupled to theserver. Notification 732 can be presented as a message and/or alert thatappears in the user interface as an informational message that does notprompt intervention on the part of the user. Furthermore, whenNotification 732 appears while another application is being used atRemote Monitoring Device 730, Notification 732 may not prompt the user(e.g., Remote Monitor) to acknowledge Notification 732, and/or evenactivate a remote monitoring application (which may be idle orinactive). In such cases, such lack of interruption can result in thecontinued use of the other application by the user. In someimplementations, Notification 732 can include time and/or locationstamps for the Host, and/or time and/or location stamps for RemoteMonitors.

Other sorts of communications can be sent through communicationchannels. In some cases, with present technologies, Hosts and/or RemoteMonitor(s) presently rely on outside communication channels tocommunicate with each other regarding the monitoring of a Host's health.Such outside communication channels can include phones, emails, texts,etc. In certain situations, using such outside communication channelsmay not only be inconvenient, but can also be unreliable for a varietyof reasons outside the control of the health monitoring system. Suchunreliability can also be platform specific, where certain devices havetheir own issues, compatibility problems, glitches, and/or otherproblems in communication. Accordingly, communications between Hostsand/or Remote Monitors (e.g., between a Host and a Remote Monitor, aHost and a Host, and/or a Remote Monitor and a Remote Monitor) and/orSecure Server 504 can include communications sent through MonitoringSystem 500. In some implementations, such communications can be sent inaddition to or as an alternative to outside communication channels. Suchcommunications can include user-entered data/messages and/orprepopulated data/messages that can be sent between one or more of HostMonitoring Devices 502A-N, Remote Monitoring Devices 508A-N, Network(s)510, Secure Server 504, Workstation 506, and/or other devices. Forexample, such communications can appear as a pop-up and/or an inbox insoftware (e.g., a computer program or mobile application) run on HostMonitoring Devices 502A-N, Remote Monitoring Devices 508A-N, Network(s)510, Secure Server 504, Workstation 506, and/or any other systemdescribed in this disclosure. In cases where glucose levels, Host and/orRemote Monitor data, and/or any process discussed in this disclosure arerun through a software application on Host Monitoring Devices 502A-N,Remote Monitoring Devices 508A-N, Network(s) 510, Secure Server 504,Workstation 506, and/or other devices, communications can be sent viathat same software application.

In some cases, such communications can be accumulated in one or morelogs. Such logs can include communications from one or more persons(e.g., Hosts and/or Remote Monitors) and/or devices (e.g., HostMonitoring Devices 502A-N, Remote Monitoring Devices 508A-N, Network(s)510, Secure Server 504, Workstation 506, and/or any other systemdescribed in this disclosure). These messages can be filtered and/orisolated for particular individuals or individual devices, and/orco-populated by a plurality of individuals and/or devices. In somecases, the contents of logs can be private to a particular device (e.g.,one of Host Monitoring Devices 502A-N, Remote Monitoring Devices 508A-N,Network(s) 510, Secure Server 504, Workstation 506, and/or any othersystem described in this disclosure), and/or can be shared across aplurality of devices (e.g., a plurality of Host Monitoring Devices502A-N, Remote Monitoring Devices 508A-N, Network(s) 510, Secure Server504, Workstation 506, and/or any other system described in thisdisclosure). As a non-limiting example, a Host using Host MonitoringDevice 502A can send a message (e.g., a communication) to one or moreRemote Monitors using Remote Monitoring Devices 508A-N. Such a messagecan say, “I'm following my treatment” or other text. As anothernon-limiting example, a message (e.g., generated by a remote monitoringdevice, host monitoring device, or server) can be stored on SecureServer 504. Secure Server 504 can then send that message to anotherdevice, such as Remote Monitoring Devices 508A-N, Host MonitoringDevices 502A-N, Workstation 506, other servers, and/or other devices.

In some implementations, communications can be user-entered and/orprepopulated. For example, prepopulated messages can be based onpatterns in analyte measurements and/or other data (e.g.,communications, Processed Data, Contextual Data, Health Information,System Information, Treatment Information, User Data, Sensor Data,Summary Data, and/or other data mentioned in this disclosure). By way ofillustrative example, Host Monitoring Device 502A can anticipate a lowerglucose reading. From Contextual Data, such as an accelerometer and/oruser-inputted data, Host Monitoring Device 502A can recognize that theHost is exercising. A prepopulated message may say to Remote Monitors,“I'm exercising,” so that Remote Monitors know the context of themeasurements. As another non-limiting example, a Host can select aprepopulated message out of a library of prepopulated messages. By wayof illustration, a Host may send a message saying “I'm going to hang outwith friends, but I'm being careful and have my insulin,” to providereassurance to Remote Monitors before the Host partakes in the activity.As another non-limiting example, prepopulated messages can generally sayin a message what a Host will or will not do (e.g., treatment, activity,medicine, etc.).

A variety of communication tools can facilitate the flow of informationbetween a Host and Remote Monitor(s) and increase the efficiency ofconveying health information to positively affect the Host's health.Various techniques, as described herein, can be utilized to assist theHost and Remote Monitor(s) to better convey information, reduce errors,reduce monitor or host fatigue, save time and increase the passion andinterest of all involved for engaging with the remote monitoring system.

For example, a smart keyboard can be utilized as a feature of the remotemonitoring system. When interacting with the host remote monitoringdevice, or automatically, the smart keyboard can determine when aparticular analyte condition (e.g., a low glucose condition) occurred oris present and generate a message to that effect. The messages can bekept short, friendly, colloquial and concise to convey informationefficiently and without distraction (e.g., “Hey, I'm 60 and dropping”).On the Remote Monitor side, the smart keyboard feature can suggest orgenerate relevant responses of a similar character (e.g., “Did youtreat?” or “How did you treat?”). Host responses can be logged as eventsas described herein. In some embodiments, the host monitoring device andthe remote monitor can include a virtual assistance feature, for examplein the form of a text bot. The virtual assistance can have access torelevant data and may be situationally aware. The virtual assistant canask questions, offer decision support or suggestions to the Host orRemote Monitor(s) based on the information gathered, the underlying Hostand/or Remote Monitor data and generate appropriate messages to belogged or transmitted between the Host and Remote Monitor(s).

In some cases, smart or dynamic sticker packs may be supported in theremote monitoring devices (of Host or Remote Monitors). Some RemoteMonitors, as described herein, may utilize SMS text messages and emojifor communications with the Host. Sticker packs can utilize images toconvey information more efficiently than text alone. Additionally,sticker packs may be interactive, allowing the Remote Monitors and Hostto collaborate in a visually pleasing medium for building a healthmanagement or treatment strategy. In some embodiments, the remotemonitoring devices of the Host and Remote Monitors can offer diabetessticker packs for common issues and responses (e.g., low glucose,dropping or rising glucose values, need for ingesting carbs, waiting apredetermined time, emotional venting about the challenges of livingwith diabetes). Dynamic sticker packs can also be incorporated, forexample via smart keyboards as described herein. Dynamic stickers canconvey dynamic information about glucose level and its future trends.For example, one dynamic sticker can be a circle and an arrow on theperimeter of the circle, where a current glucose reading is displayed inthe center of the circle and the location of the arrow on the perimeterof the circle can indicate a projection of a future direction of glucosevalues. Other dynamic stickers can be visuals conveying insulin on board(JOB) value, trend graphs or other visuals relevant to management ofdiabetes. To further simplify and facilitate efficient communicationbetween the Host and Remote Monitors, relevant stickers or visuals basedon present conditions can be offered to the Host and Remote Monitors.For example, when a low glucose value is detected, visuals or stickersrelevant to the low glucose condition (e.g., a visual instructingconsumption of carbs) can be presented in a convenient fashion for theRemote Monitor to choose to include in its communication with the Host.In a communication session, for example, via SMS, the Host and RemoteMonitor can utilize visuals, dynamic visuals, stickers, text, emoji orother available communication tools to collaboratively build a treatmentstrategy.

In some embodiments, an application running on the remote monitoringdevices can support wearable smart devices such as smart watches, smartglasses or similar devices to communicate rich notifications, allowingthe Host and/or the Remote Monitor to quickly communicate without havingto navigate or hunt for information through complicated menus. Intuitivegraphical design interfaces can be used to deliver real-time or nearreal-time event sharing between the Host and Remote Monitor using richnotification techniques. For example, a dashboard view can provide quickglance overview of key health parameters important to diabetes patients(e.g., current glucose values, projected trends, charts, etc.). Richnotification techniques can be used, for example via a slide down menuon a smart wearable device (e.g., a smart watch), where dynamicnotifications, such as current location of the Host or Remote Monitor,can be viewed. Frequently accessed menu options may also be integratedwithin a slide down application menu on a smart wearable device forefficient access. For example, the Remote Monitor can choose betweenoptions such as acknowledging notifications, calling the Host or textingthe Host via the slide down application menu. As described herein,prepopulated and frequently used messages may be made available to theHost and Remote Monitors to select without having to type or dictatethese messages (e.g., “Are you OK?” or “I took care of it.”).Prepopulated text messages or graphics facilitate easy and efficientcommunication between all involved to better manage diabetes or otherhealth issues.

A feature of the disclosed remote monitoring systems described herein isthe real time or near real time sharing of Host data with RemoteMonitors. Accordingly, communications between the Host and RemoteMonitors can benefit from instant or near instant sharing of messagesincluding suggestions and/or encouragements. For example, customized orpersonalized messages can be generated and presented to the Host andRemote Monitors to encourage healthy behavior and provide community andsupport as the Host and loved ones deal with the challenges of managingdiabetes or other health conditions. The process can encourage otherRemote Monitors (e.g., family members) who may be at risk to adopthealthy behavior and understand the challenges. As described, thecustomized or personalized messages may be short, friendly, colloquialand concise (e.g., “Your numbers look great today! Thanks, Dad.”).Suboptimal results can also trigger alerts to Remote Monitors (e.g.,health coaches, family members, health care professionals, etc.). Insome embodiments, personalized dashboards may be used to track and holdthe Host accountable. Undesirable trends can trigger personalized“social” alerts, video calls, voice calls, text messages, social mediaposts, etc. to influence Host's health trends in a healthy direction.

FIG. 8 illustrates a graphical depiction of an example system having ahost monitoring device, a plurality of remote monitoring devices, aserver, and networks. Monitoring System 800 can include Host 809. Host809 can have a plurality of devices. For example, Host 809 can haveMedicament Delivery Pump 802, which can be configured to deliver amedicament such as insulin (e.g., a glucagon pump). Host 809 can alsohave Glucose Meter 804 (e.g., a blood finger stick meter), and/or anyother device and/or sensor. Host 809 can also have Host MonitoringDevice 808, which can include Sensor Electronics 812, Continuous AnalyteSensor 810, and/or any component substantially similar to HostMonitoring Device 200.

In some implementations, Host Monitoring Device 808 can communicativelycouple (e.g., wirelessly, wired, and/or the like) with one or moredevices, such as Receiver 811 and the like, presenting (and/or alerting)information, such as sensor information transmitted by Host MonitoringDevice 808 for display at Receiver 811. Receiver 811 can be a separatecomponent or integrated into Host Monitoring Device 808. Receiver 811can include one or more interfaces, such as machine-to-machineinterfaces and/or user interfaces. For example, such user interfaces caninclude a variety of interfaces, such as any of the interfaces describedwith respect to User Interface 208. The components that include the userinterface may provide controls to interact with the user (e.g., theHost). One or more buttons can allow, for example toggle, menuselection, option selection, status selection, yes/no response toon-screen questions, a “turn off” function (e.g., for an alert), a“snooze” function (e.g., for an alert), a reset, and/or the like. Adisplay (e.g., a LCD screen or any other display described in thisdisclosure) can provide the user with, for example, visual data output.An audio transducer (e.g., a speaker) can provide audible signals inresponse to triggering of certain alerts, such as present and/orpredicted hyperglycemic and hypoglycemic conditions. In some exampleimplementations, audible signals can be differentiated by tone, volume,duty cycle, pattern, duration, and/or the like. In some exampleimplementations, the audible signal can be configured to be silenced(e.g., snoozed or turned off) by pressing one or more buttons ofReceiver 811 and/or by signaling the Sensor Electronics 812 using abutton or selection on Receiver 811. Receiver 811 can be communicativelyand/or operatively coupled to Gateway 819, which can give network accessto Receiver 811.

Medicament Delivery Pump 802, Glucose Meter 804, Host Monitoring Device808, Receiver 811, and/or Gateway 819 can each be communicativelycoupled to one or more networks, such as Networks 813, 814, 815. In somecases, there can be other modes of communication, such as notificationservices (e.g., Notification Service 816), which can be configured totransmit communications, such as notifications, alerts and/or othercommunications described in this disclosure. Capabilities of those othermodes of communications can also be incorporated into Networks 813, 814,815.

In example implementations, Secure Server 817 (which can besubstantially similar to Secure Sever 504) can receive a communication(e.g., notification and/or message) from Notification Service 816,and/or otherwise (e.g., directly from Remote Monitoring Device 818A-Nand/or Host Monitoring Device 808) that a remote monitoring device isout of service or otherwise unreachable, in which case, Secure Server817 can resend the notification and/or message to a different remotemonitoring device. By way of illustrative example, suppose there areRemote Monitoring Devices 818A-N. Remote Monitoring Device 818A had amalfunction and was unreachable. Secure Server 817 could resend anynotification and/or message that was supposed to go to Remote MonitoringDevice 818A to Remote Monitoring Device 818B. Similarly, where a device(e.g., Remote Monitoring Device 818A-N and/or Host Monitoring Device808) is unable and/or unavailable to send a communication, Secure Server817 can send such communication. For example, Remote Monitoring Device818A could request a previous analyte measurement from Host MonitoringDevice 808. However, in this example, Host Monitoring Device 808 couldbe temporarily unavailable (e.g., due to network and/or device issues).Secure Server 817 could have stored in memory Host Monitoring Device808's previous analyte measurement and send it to Remote MonitoringDevice 818A.

Secure Server 817 can use a delay for resending communications (e.g.,notifications, alerts, messages, and/or any other communicationdescribed in this disclosure). Such a delay can be configured based onthe severity and/or type of the event, and/or Secure Sever 817 can alsoinclude rules defining a predetermined quantity of unsuccessful resends(e.g., 1, 2, 3, 4, 5, 6, or more resends) before escalation to anotherremote monitoring device, a secondary/backup monitor, an emergencymedical service, and the like. And, this predetermined quantity ofunsuccessful resends can also be configured at Secure Server 817 to varybased on severity and/or type of the event and/or be user configured.

In some implementations, as described in this disclosure, additionalinformation about a Remote Monitor can also be desirable in order toprovide better care for a Host and/or to enhance relationships betweenHosts and/or Remote Monitors. In some cases, a Remote Monitor in onesystem can even be a Host him/her self in the same system and/or anothersystem. In some cases, the Remote Monitor may not be a Host per se, butprovide data from his/her devices to a server, host monitoring device,and/or other devices. These other devices can provide context and/orallow a monitoring system to adaptively and/or contextually adjustcommunication settings (e.g., frequency, type, kind, etc.) and/orclassifications based on such data from the Remote Monitor's devices.

Example Remote Monitor 859, who can be associated with one or more ofRemote Monitoring Devices 818A-N can also have devices communicativelycoupled to Remote Monitoring Devices 818A-N, Networks 813, 814, 815,Secure Server 817, Notification Service 816, Medicament Delivery Pump802, Glucose Meter 804, Host Monitoring Device 808, and/or any device inMonitoring System 800. For example, Remote Monitor 859 can haveMedicament Delivery Pump 862, which can be configured to deliver amedicament such as insulin (e.g., a glucagon pump). Remote Monitor 859can also have Glucose Meter 854 (e.g., a blood finger stick meter),and/or any other device and/or sensor. Remote Monitor 859 can also haveDevice 858, which can include Sensor Electronics 852, Continuous AnalyteSensor 850. Remote Monitor 859 can also have other devices, such ashealth rate monitors, activity trackers, pulse oximeters, wearables(e.g., smart watches, smart rings, workout monitors,electrocardiographs, bioimpedence sensors, breathing monitors, sleepmonitors, posture monitors, habit detectors, temperature trackers,fabrics embedded with sensors, moisture detectors, etc.),accelerometers, gyroscopes, speedometers, pedometers, blood pressurereaders, pump data for administration of other drugs, drug sensors(e.g., breathalyzers and sensors configured to measure intoxication orpresence of drugs), medical devices, and/or other devices that measure acharacteristic of the Remote Monitor and/or is described in thisdisclosure.

FIG. 9 illustrates a diagram showing example signals transmitted betweena host monitoring device, network(s), and a remote monitoring device.Example Monitoring System 900 includes Host Monitoring Device 902,Network(s) 904, and Remote Monitoring Device 906. In someimplementations, Host Monitoring Device 902 can be substantially similarto Host Monitoring Device 200 and/or any host monitoring devicementioned in this disclosure, and/or can be configured to performprocesses similar to Process 100 and other processes described in thisdisclosure. Similarly, in some implementations, Remote Monitoring Device906 can be substantially similar to Remote Monitoring Device 300 and/orany remote monitoring device mentioned in this disclosure, and/or can beconfigured to perform processes similar to Process 150 and otherprocesses described in this disclosure. Communications (e.g., data,information, messages, notifications, alerts, responses, signals, etc.)can pass between Host Monitoring Device 902, Network(s) 904, and/orRemote Monitoring Device 906. Host Monitoring Device 902 and/or RemoteMonitoring Device 906 can use communicators (e.g., communicatorssubstantially similar to Communicators 207, 307) for suchcommunications. Network(s) 904 can be substantially similar toNetwork(s) 510 and/or any network(s) described in this disclosure, andcan also include a server (e.g., a server substantially similar toSecure Server 504 and/or any other server described in this disclosure)and/or a workstation (e.g., a workstation substantially similar toWorkstation 506 and/or any other workstation described in thisdisclosure). Network(s) 904 can communicatively and/or operativelycouple to a server (e.g., a secure server substantially similar toSecure Server 504) and/or a processor to process, relay, and/or storedata and/or information it receives and/or sends.

In some cases, it can be desirable that signals are not immediately orsubstantially immediately (e.g., as quickly as the signal can beprocessed and/or sent) passed from Host Monitoring Device 902 to RemoteMonitoring Device 906. For example, a Host associated with HostMonitoring Device 902 can sometimes address the subject of an alert toRemote Monitoring Device 906 relatively quickly and/or inconsequentiallywithout involving the Remote Monitor associated with Remote MonitoringDevice 906. By way of illustrative example, Host Monitoring Device 902could send an alert that shows a low glucose level that could cause aRemote Monitor associated with Remote Monitoring Device 906 unwarrantedconcern and worry, and could suggest that the Host associated with HostMonitoring Device 902 could need immediate assistance. However, thatHost may have already realized the issue and could immediately eatsomething to raise his/her glucose in response, making the low glucoselevel a non-issue. In such cases, it may be desirable to delay orprevent alarming notifications from going to Remote Monitoring Device906 where such issues are already addressed.

As another example, a Host may not want to cause disruption or worry toRemote Monitors when an alert has been addressed and/or treated by theHost. For example, some alert settings may be programmed“conservatively,” where an alert is more easily triggered by a glucoseconcentration measurement not within, but close to, upper or lowerthreshold glucose measurements, a duration of measurements threshold, orby a defined combination of measurement and duration. If the Host hasaddressed his/her situation, he/she may want to shield the RemoteMonitors from being alerted to a situation under control/managed.

In some implementations, an intentional delay can be built into signaltransmission between Host Monitoring Device 902, Network(s) 904, and/orRemote Monitoring Device 906. By way of illustration, Network(s) 904 canhave a built-in delay (e.g., a delay stored in a server and/or othernetwork hardware and/or software) where after signals are received byNetwork(s) 904 from Host Monitoring Device 902 and/or Remote MonitoringDevice 906, Network(s) 904 does not immediately (and/or substantiallyimmediately) send a corresponding communication. Rather, Network(s) 904can delay a predetermined amount of time. Such predetermined amount oftime can be set by a Host through Host Monitoring Device 902, a RemoteMonitor through Remote Monitoring Device 906, factory programming,hardcoding, firmware and/or software, operators, Network(s) 904, and/orany way of adjusting an operational parameter. As non-limiting examples,such delays can be seconds (e.g., 0, 1, 5, 10, 15, 20, 25, 30, or moreseconds, or any amount of time between the aforementioned seconds),minutes (e.g., 0, 1, 5, 10, 15, 20, 25, 30, or more minutes, or anyamount of time between the aforementioned minutes), or hours (e.g., 0,1, 5, 10, 15, 20, 25 or more hours, or any amount of time between theaforementioned hours). In some cases, different delays can be used fordifferent events. In those cases, enough time can be given for areasonable Host to respond. This amount of time can take into accountcontext (e.g., Contextual data), patterns in Host or Remote Monitorbehavior, time of day, and/or other factors. For example, afterreceiving from Host Monitoring Device 902 a low glucose measurement andan alert of such around lunch time, Network(s) 904 can delay 30 minutesto see if Host's glucose increases (e.g., by eating something). If noincrease has occurred, Network(s) 904 can forward on a notificationtelling Remote Monitoring Device 906 that Host Monitoring Device 902 hasa low glucose measurement and may need assistance. If an increase hasoccurred, Network(s) 904 can forward on the data, but not give an alertor say that the Host may need assistance.

As another non-limiting example, a Host can have a glucose level spikeafter dinner every day that reduces within an hour of the spike withoutconsequence. By recognizing the daily pattern of that spike, Network(s)904 can delay sending any notifications that would alert a RemoteMonitor of the spike until more than an hour has passed and the glucoselevel has not reduced as it typically would.

In some implementations, the delay can be event-triggered instead ofbased on time. For example, Host Monitoring Device 902, Network(s) 904,and/or Remote Monitoring Device 906 can wait for a certain number ofmeasurements with a determined characteristic (e.g., above or below athreshold) before sending a communication. By way of illustrativeexample, Host Monitoring Device 902 could have an analyte measurementbelow a lower threshold of analyte measurements. A communication basedon this low measurement may not be sent immediately and/or substantiallyimmediately. Instead, a Host Monitoring Device 902 can wait until five(5) (or any determined number of measurements) analyte measurementsbelow the lower threshold have been measured, and if that event occurs,then send the communication. A similar process can be performed by aRemote Monitoring Device and/or Network(s) 904.

In some implementations, Network(s) 904, Host Monitoring Device 902and/or Remote Monitoring Device 906 can have substantially similardelays. For example, Remote Monitoring Device 906 can delay sending acommunication at the front end. Similarly, Remote Monitoring Device 906can delay displaying a received communication at the back end.Network(s) 904, including a server, can hold onto communications beforerelaying them to Remote Monitoring Device 906 and/or Host MonitoringDevice 902.

For example, the delay can be threshold-based where a host monitoringdevice (e.g., a host monitoring device substantially similar to the HostMonitoring Device 902, 502 or other) generates an alert for the Hostwhen the Host's analyte level is determined to exceed a first threshold(e.g., a moderate threshold to generate an alert to the Host) but not asecond threshold (e.g., an extreme threshold indicative of a dangerousanalyte level). In such instances, for example, a server (e.g., a secureserver substantially similar to Secure Server 504) may receive the alertfrom the Host Monitoring Device and/or may generate the alert based onthe analyte data received by the server from the host monitoring device.The server will delay providing notifications to the remote monitoringdevices pertaining to Host's analyte level exceeding the firstthreshold, for a predetermined amount of time. This may allow the Hostto take action regarding his/her analyte level and can alleviate theneed for having to provide the notification to the remote monitoringdevice(s). In such instances, the server can monitor the Host's responseto the alert by monitoring the Host's analyte level after the alert. Forexample, if the Host's analyte level returns to a level that does notexceed the first threshold, then the server can close the alert and notgenerate any notifications to the remote monitoring device(s). If, forexample, the Host's analyte level does not return to a level that doesnot exceed the first threshold (e.g., remains exceeding the firstthreshold), then the server can provide the notifications to the remotemonitoring device(s) based on the notification rules associated with therespective remote monitoring device(s). In some implementations, forexample, the server can send a communication to the Host to remind theHost to take an action associated with the analyte level or to prompt aresponse from the Host to acknowledge he/she is aware of the alertand/or is taking action to remedy the analyte level exceeding the firstthreshold. In such instances, for example, if the Host responds andconfirms that action has been taken, then the server can continue thedelay (e.g., within the predetermined period and/or provide an extensionperiod of delay) and monitor the Host's monitoring the Host's analytelevel to make sure it returns to a level not exceeding the threshold. Ifthe analyte level does not return to a level not exceeding the thresholdin the predetermined time period or extension period, the server cansend a follow up communication (e.g., reminder or prompt for response)to the host monitoring device, and/or the server can remove the delayand reinitiate the process to notify the appropriate remote monitoringdevice(s). In this example, the system can keep non-urgent alertsprivate to the Host, which can avoid unnecessarily disturbing the RemoteMonitors.

Host Monitoring Device 902 can generate Signal 908 and send Signal 908(e.g., via a communicator such as Communicator 207) to Network(s) 904,which may also receive Signal 908 via a communicator substantiallysimilar to Communicators 207, 307. Signal 908 can include data based ondata from analyte sensor(s) and/or other device(s). For example, analytesensor(s) can include glucose levels measured by a CGM and/or othersensor(s). The analyte sensor(s) and/or other device(s) can generatedata including, Contextual Data (e.g., time/amount/type of medicament(e.g., insulin, sulfonylureas, biguanids, meglitinides,thiazolidinediones, DPP-4 inhibitors, SGLT2 inhibitors,alpha-glucosidase inhibitors, bile acid sequestrants, and/or other drugsor treatments) taken, time/amount/type of food (e.g., carbohydrates,protein, dairy, fat, fruits, vegetables, candy, dessert, sugars,calories, quantities, preparations, etc.) ingested, time/amount/type ofexercise or activity undertaken (e.g., running, walking, sports, weightlifting, sitting, sleeping, idle, resting, etc.), level of stress felt(e.g., acute, episodic acute, emotional, chronic, high stress, mediumstress, low stress, no stress, anxiety, panic attack, etc.), environment(e.g., weather, humidity, pressure, temperature, etc.) and/or location,time of day, and/or any other Contextual Data), Processed Data, HealthData, System Data, Treatment Data, User Data, Sensor Data, Summary Data,and/or any data described in this disclosure, and/or patterns and/orcombinations of any of the aforementioned. Signal 908 can include suchgenerated data, or data based on such generated data. Network(s) 904 canreceive Signal 908 and store, relay, and/or process Signal 908.

Signal 910 can include data based on data from analyte sensor(s) and/orother device(s), such as data based on Signal 908 received by Network(s)904. Remote Monitoring Device 906 can receive Signal 910 via acommunicator.

In some cases, Signal 910, and other signals discussed with reference toFIG. 9, can be adaptive and/or contextual, in which certain events,measurements, and/or patterns of the foregoing allow for signals to besent. For example, signals can be sent in response to measurements aboveor equal to a certain threshold, measurements below or equal to acertain threshold, determined amounts of oscillations, particular ratesof change (e.g., fast rising or fast falling measurements), outliers,stability over a determined time (e.g., measurements falling within adefined range), activities (e.g., working out, eating, homework,walking, etc.), events (e.g., rock concert, movie, etc.), patterns inother data (e.g., in response to measurements of heart rate,temperature, acceleration, and/or any other data from any devicedescribed in this disclosure), and the like.

Remote Monitoring Device 906 can send Signal 916, which can include databased on data from Remote Monitoring Device 906. Such data from RemoteMonitoring Device 906 can include data about the Remote Monitorincluding, but not limited to, data based on data from analyte sensor(s)and/or other device(s). For example, analyte sensor(s) can includeglucose levels measured by a CGM and/or other sensor(s). The analytesensor(s) and/or other device(s) can generate data including, ContextualData (e.g., time/amount/type of medicament (e.g., insulin,sulfonylureas, biguanids, meglitinides, thiazolidinediones, DPP-4inhibitors, SGLT2 inhibitors, alpha-glucosidase inhibitors, bile acidsequestrants, and/or other drugs or treatments) taken, time/amount/typeof food (e.g., carbohydrates, protein, dairy, fat, fruits, vegetables,candy, dessert, sugars, calories, quantities, preparations, etc.)ingested, time/amount/type of exercise or activity undertaken (e.g.,running, walking, sports, weight lifting, sitting, sleeping, idle,resting, etc.), level of stress felt (e.g., acute, episodic acute,emotional, chronic, high stress, medium stress, low stress, no stress,anxiety, panic attack, etc.), environment (e.g., weather, humidity,pressure, temperature, etc.) and/or location, time of day, and/or anyother Contextual Data), Processed Data, Health Data, System Data,Treatment Data, Summary Data, Sensor Data, and/or any data described inthis disclosure, and/or patterns and/or combinations of any of theaforementioned. Similarly, Network(s) 904 can receive data based on datafrom each of the respective other remote monitoring device(s).Accordingly Network(s) 904 can receive Signal 908 and/or data from anyother remote monitoring device(s), and store, relay, and/or processSignal 908 and/or data from any other remote monitoring device(s).

Network(s) 904 can then send Signal 912 to Host Monitoring Device 902.Signal 912 can include data based on data from remote monitoringdevice(s), such as Remote Monitoring Device 906 and/or any other remotemonitoring device. Similarly, Network(s) 904 can send Signal 914 toRemote Monitoring Device 906, where Signal 914 can include data based ondata from other remote monitoring device(s).

Hosts associated with Host Monitoring Device 902 and Remote Monitorsassociated with Remote Monitoring Device 906 each can have one or moreother device(s) that can be communicatively coupled (e.g., viacommunicators substantially similar to Communicators 207, 307) directlyto Host Monitoring Device 902 and/or Remote Monitoring Device 906,respectively, and/or coupled to Network(s) 904. In the case where thoseother device(s) are coupled to Network(s) 904 (and/or may or may not becoupled to Host Monitoring Device 902 and/or Remote Monitoring Device906 directly), those devices can send data to Network(s) 904, including,Contextual Data (e.g., time/amount/type of medicament (e.g., insulin,sulfonylureas, biguanids, meglitinides, thiazolidinediones, DPP-4inhibitors, SGLT2 inhibitors, alpha-glucosidase inhibitors, bile acidsequestrants, and/or other drugs or treatments) taken, time/amount/typeof food (e.g., carbohydrates, protein, dairy, fat, fruits, vegetables,candy, dessert, sugars, calories, quantities, preparations, etc.)ingested, time/amount/type of exercise or activity undertaken (e.g.,running, walking, sports, weight lifting, sitting, sleeping, idle,resting, etc.), level of stress felt (e.g., acute, episodic acute,emotional, chronic, high stress, medium stress, low stress, no stress,anxiety, panic attack, etc.), environment (e.g., weather, humidity,pressure, temperature, etc.) and/or location, time of day, and/or otherContextual Data), Processed Data, Health Data, System Data, TreatmentData, User Data, Sensor Data, Summary Data, and/or any data described inthis disclosure, and/or patterns and/or combinations of any of theaforementioned. Network(s) 904 can receive such data from thosedevice(s) and/or store, relay, and/or process that data. Network(s) 904can then send Signal 918 to Host Monitoring Device 902. Signal 918 caninclude data based on data from those other device(s). Similarly,Network(s) 904 can send Signal 920 to Remote Monitoring Device 906,where Signal 920 can include data based on data from those otherdevice(s).

As mentioned in this disclosure, in some implementations, communications(e.g., notifications, messages, alerts, and/or any communicationsdescribed in this disclosure, including but not limited tocommunications discussed with reference to FIG. 7B-C and FIG. 14D) canbe sent between one or more of Host Monitoring Device 902, Network(s)904, and/or Remote Monitoring Device 906 using communicators (e.g.,communicators substantially similar to Communicators 207, 307). Wheresuch communications are between Host Monitoring Device 902 and RemoteMonitoring Device 906, such communications can be sent directly betweenthem and/or through Network(s) 904. For example, Signal 922 can includecommunications from Host Monitoring Device 902 sent to Network(s) 904.Network(s) can receive, store, relay, and/or process Signal 922 and/orother communications (e.g., from host monitoring devices and/or otherdevices), and send Signal 924 to Remote Monitoring Device 906, whereSignal 924 is based on the communications received by Network(s) 904.Similarly, Signal 928 can include communications from Remote MonitoringDevice 906 sent to Network(s) 904. Network(s) 904 can receive, store,relay, and/or process Signal 928 and/or other communications (e.g., fromremote monitoring devices and/or other devices) and/or send Signal 926to Host Monitoring Device 902, where Signal 926 is based on thecommunications received by Network(s) 904.

Based on the reception of communications, Host Monitoring Device 902,Remote Monitoring Device 906, and/or other devices can send responses tocommunications, such as messages, acknowledgements, notifications,alerts, dismissals, feedback, error messages, etc. For example, HostMonitoring Device 902 can send Signal 930 to Network(s) 904, whereSignal 930 is a response to a communication received by Host MonitoringDevice 902. Network(s) 904 can receive, store, relay and/or processSignal 930 and/or other responses to communications (e.g., from hostmonitoring devices and/or other devices), and send Signal 932 to RemoteMonitoring Device 906, where Signal 930 is based on the responses tocommunications received by Network(s) 904. Similarly, Signal 936 caninclude responses to communications from Remote Monitoring Device 906sent to Network(s) 904. Network(s) 904 can receive, store, relay, and/orprocess Signal 936 and/or other responses to communications (e.g., fromremote monitoring devices and/or other devices) and/or send Signal 934to Host Monitoring Device 902, where Signal 934 is based on theresponses to communications received by Network(s) 904.

FIG. 10 illustrates a predictive calculation based on measured data of aHost. In some cases, a Remote Monitor and/or Host can desire to not onlyknow analyte measurements that have already occurred, but also futureprojections and/or predictions of analyte measurements. Such capabilitycan allow Hosts and/or Remote Monitors to prepare for the future and/orallow for present planning of treatment. In the case of diabetes, a CGMcan collect data and a host monitoring device, remote monitoring,server, and/or other device can perform a predictive calculation.

In some implementations a host monitoring device (e.g., substantiallysimilar to Host Monitoring Device 200 and/or perform processessubstantially similar to Process 100), remote monitoring device(substantially similar to Remote Monitoring Device 300 and/or performprocesses substantially similar to Process 150), servers (e.g., SecureServer 504), and/or other device can display a graph, such as Graph 1012in Display 1014. Graph 1012 can include discrete measurements that aredisplayed as points on Graph 1012, such as Points 1008, 1010. In someimplementations, the host monitoring device, remote monitoring device,and/or other device can display Graph 1012 as a continuous curve inwhich the displaying device receives a continuous (e.g., analog) orsubstantially continuous stream of points, and/or interpolates betweendiscrete points. Such interpolation can be performed by the hostmonitoring device, remote monitoring device, server, and/or otherdevice.

In some implementations, points in Graph 1012 can be selected forfurther information. For example, Point 1010 can be selected to displayits value (e.g., the EGV associated with Point 1010). That value can bedisplayed in Display 1020. Other information can be displayed in thedisplay as well. For example, Processed Data, Contextual Data, HealthData, System Data, Treatment Data, User Data, Sensor Data, Summary Data,communications, and/or any data described in this disclosure can bedisplayed in Display 1020 or elsewhere on the display of a remotemonitoring device, host monitoring device, and/or other device.

Display 1014 can include determined thresholds for Graph 1012. Suchthresholds can be indicative of a measuring event that will trigger anaction. Such thresholds can be determined and/or inputted by a Host,Remote Monitor, health practitioner, or others. As a non-limitingexample, where Graph 1012 includes glucose measurements, and each point(e.g., Points 1008, 1010) is indicative of a glucose concentration,thresholds can indicate the values of measurements that trigger analert, alarm, communication, or other event. Lower Threshold 1018 can bea lower threshold in which measurements at or below the determined valueof the threshold (e.g., glucose concentration) trigger the alert, alarm,communication, and/or other event. Similarly, Upper Threshold 1016 canbe an upper threshold where measurements at or above the determinedvalue of the threshold trigger the alert, alarm, communication, and/orother event.

Display 1014 can show predictive measurements, such as Predictive Points1004, 1006. Such points can be extrapolated from Graph 1012 usingextrapolation that takes into account one or more points (e.g.,measurements of an analyte such as glucose concentration) of Graph 1012.Such extrapolation techniques can include linear extrapolation,polynomial extrapolation, conic extrapolation, French curveextrapolation, forecasting, multigrid methods, predictive intervals,regression analysis, Richardson extrapolation, trend estimation, domainanalysis, and/or any other extrapolation technique known in the art.Such predictive measurements can be shown in Display 1014 or calculatedand displayed as number values or otherwise.

In some implementations, additional outputs and/or determinations can bedisplayed in Display 1014. For example, rate of change, treatmentsuggestions, and/or future projections can be displayed. Line 1002 is anon-limiting example of a rate of change displayed in Display 1014. Line1002 illustrates the rate of change at Point 1008. Line 1002 can be usedto predict future values, such as Predictive Points 1004, 1006, whichcan be projected along Line 1002 as possible future measurements.Advantageously, in this example, Line 1002 shows a downward trend in theHost's glucose concentration. Using Line 1002 and/or Predictive Points1004, 1006, a Host and/or Remote Monitor viewing Display 1014 cananticipate that the Host's glucose level will return to normal levels,and also see the approximate time in which that may happen. In someimplementations, a curve can be fitted to Graph 1012, and predictivepoints estimated by the curve. Example curve fitting techniques includeleast squares and other known algorithms.

Additional signal processing can be performed on Graph 1012 as well.There can be additional, illuminating information that can be extractedfrom analyte measurements such as glucose levels. For example, suchinformation can include the amount of oscillation in measurements, thenumber of times thresholds are crossed, comparisons to other curves,removal of outliers, and/or other desired information. Such can bemeasured and/or displayed as desired. Such signal processing can beperformed using Fourier Transform, convolution, correlation, autocorrelation, cross-correlation, covariance, etc. In some implementation,signal processing can include outlier and/or malfunction detection. Suchcan be detected and/or controlled through noise filters, correlation,auto calibration, and/or other techniques.

In some cases, it can be desirable to get more information about thecontext in which a measurement was taken. Such context can allow a Hostand/or Remote Monitor to better understand the measurement and possiblefuture treatments. In some implementations, each point (e.g., Points1008, 1010) can be selectable to bring up an additional screen thatgives more information about the context of that point. In some cases,such information can include data such as communications, ProcessedData, Contextual Data, Health Data, System Data, Treatment Data, UserData, Sensor Data, Summary Data, and/or any data described in thisdisclosure, as well as data based on the aforementioned.

FIG. 11 illustrates an example log that can be displayed for a datapoint on the graph of FIG. 10. For example, selecting Point 1010 in FIG.10 could cause the display to show Log 1100. By way of illustrativeexample, Log 1100 can show details such as user entered information(e.g., “Ate and got insulin bolus”), temperature, heart rate, bloodoxygen level, activities entered, statuses/logs of other devices (e.g.,medicament pump), locations, information about Remote Monitors, and/orhistorical logs. In some cases, additional information and/or data canbe displayed by selecting any of the aforementioned (e.g., selecting thewords with a touch on a touch screen, a mouse on a monitor, etc.). Suchadditional information can include historical data, notes, details aboutthe measuring sensors (e.g., model, make, status, operationalparameters, settings (e.g., adjustable or non-adjustable)), and thelike. For example, historical logs can be more information about theaforementioned or other data (e.g., analyte measurements,communications, Processed Data, Contextual Data, Health Data, SystemData, Treatment Data, User Data, Sensor Data, Summary Data, and/or anydata described in this disclosure, as well as data based on theaforementioned) that can be used to provide more context of a particularmeasurement. By selecting historical logs, an additional screen canappear providing a log with information about past measurements. In someimplementations, Detail 1102 can be a link that when selected can showadditional information about Remote Monitors. For example, an additionaldisplay can provide details about a Host's Remote Monitors. Similarly,in some implementations, Detail 1104 can be a link that when selectedcan show additional historical data logs detailing data collected (e.g.,analyte measurements, communications, Processed Data, Contextual Data,Health Data, System Data, Treatment Data, User Data, Sensor Data,Summary Data, and/or any data described in this disclosure, as well asdata based on the aforementioned). For example, Detail 1104 can open adisplay that shows Retrospective Data that chronicles activities of aHost entered (e.g., by a Host, Remote Monitor, and/or other user) and/orautomatically detected by a host monitoring device and/or server.

By way of illustrative example, Log 1100 can be displayed on the displayof a host monitoring device (e.g., a host monitoring devicesubstantially similar to Host Monitoring Device 200 and/or performprocesses substantially similar to Process 100). In such a case, Log1100 can show information related to a Host using that host monitoringdevice. As a result, Log 1100 can give Host information about his/herown activities and therapies to put measurements into context. Forexample, a Host may be viewing Display 1014 as illustrated in FIG. 10and/or desire more information about a particular point.

By way of illustrative example, Log 1100 can be displayed on the displayof a remote monitoring device (e.g., a remote monitoring devicesubstantially similar to Remote Monitoring Device 300 and/or performprocesses substantially similar to Process 150). A Remote Monitor canview Log 1100 in order to give context to Host information. For example,a Remote Monitor may be viewing Display 1014 as illustrated in FIG. 10and desire more information about a particular point.

As another non-limiting example, Log 1100 can be a log stored (e.g., inmemory and/or any other data storage described in this disclosure) on aserver (e.g., a secure server substantially similar to Secure Server504). Such a log can be viewed on a display communicatively coupled tothe server, and/or on remote monitoring devices and/or host monitoringdevices communicatively coupled to the server.

FIG. 12 illustrates an example page showing information about RemoteMonitors. Page 1200 can be displayed on a host monitoring device, remotemonitoring device, and/or other device described in this disclosure. Insome implementations, Page 1200 can be stored on a server and/ordisplayed on a display operatively and/or communicatively coupled to theserver. Page 1200 can include cells, such as Cells 1202, 1214, 1216,which can each correspond to different Remote Monitors. Each cell candisplay information about the Remote Monitors, including their names,statuses (e.g., Status 1204), messages they have sent (e.g., MessageDisplay 1206), classifications (e.g., Classifications 1210, 1218),and/or graphical indications of their statuses (e.g., GraphicalIndication 1208, which can indicate the overall status of a RemoteMonitor). In some implementations, a user can select the cells of RemoteMonitors to see more information about the Remote Monitors (e.g.,communications, analyte measurements, Processed Data, Contextual Data,Health Data, System Data, Treatment Data, User Data, Sensor Data,Summary Data, and/or any data described in this disclosure, as well asdata based on the aforementioned). Such information can be pulled from aremote monitoring device, host monitoring device, server, other device,and/or any other system described in this disclosure. Advantageously,Page 1200 allows a viewer (e.g., Host and/or Remote Monitor) to quicklyview a user interface to see the status and/or relationship of RemoteMonitors. Although the example illustrated in FIG. 12 refers to glucoselevels and specific types of messages and icons, other types of events,messages, and icons discussed herein may be used to convey the status ofa host.

In the case where a Host is viewing Page 1200 on a host monitoringdevice, Page 1200 can give the Host information about his/her RemoteMonitor(s). Such information can be desirable in order for the Host tosee the status and/or relevant information about each of his/her RemoteMonitors. In the case where a Remote Monitor is viewing Page 1200 on aremote monitoring device, Page 1200 can give the Remote Monitorinformation about other Remote Monitors so that care for a Host can becoordinated. In some cases, some Remote Monitors can be anonymous tosome viewers (e.g., Hosts or Remote Monitors), where some or all of theidentifying information of a Remote Monitor (e.g., name, serial number,etc.) can be not listed. As another non-limiting example, Page 1200 canbe stored (e.g., in memory or any other data storage described in thisdisclosure) on a server (e.g., a secure server substantially similar toSecure Server 504). Such a page can be viewed on a displaycommunicatively coupled to the server or on remote monitoring devicesand/or host monitoring devices communicatively coupled to the server.

In some cases, it can be desirable for a Host and/or Remote Monitor tocompare measurements to other data, such as historical datameasurements. In some cases, a display on a host monitoring device,remote monitoring device, and/or other device can show such historicaldata measurements as numbers, graphs, or otherwise. In some cases, suchhistorical data can be presented and/or overlaid with current and/orrecent measurements. In some cases, such historical data can bedisplayed non-graphically, such as a table of numbers, lists, logs, etc.

FIGS. 13A-D illustrate historical Host data overlays that can be viewedwith Host data. One or more overlays can be used to serve as comparisonson how a Host behaved in similar, and/or substantially similar,circumstances, and how the Host's analyte measurements (e.g., glucoselevels) reacted. Similarities can be determined by comparisons. Forexample, historical data can be stored in memory, analyzed, and/ordisplayed in a remote monitoring device (e.g., Remote Monitoring Device300), host monitoring device (e.g., Host Monitoring Device 200), server(e.g., Secure Server 504), and/or any other device described in thisdisclosure. By way of illustrative example, Displays 1314, 1324, 1334,1344 can be displayed on a remote monitoring device so that a RemoteMonitor can view and/or analyze measurements of a Host in which theRemote Monitor is interested. As another non-limiting example, a Hostmay view Displays 1314, 1324, 1334, 1344 on a host monitoring device inorder to view and/or analyze his/her own measurements. As anothernon-limiting example, Displays 1314, 1324, 1334, 1344 and/or thedata/information contained within can be stored in memory on a server,and/or displayed on a display communicatively and/or operatively coupledto that server. In some cases, that server can transmit Displays 1314,1324, 1334, 1344 to a host monitoring device, remote monitoring device,and/or any device described in this disclosure.

Comparison methods between current and/or recent measurements to thathistorical data can be used. Such comparison methods can include,without limitation correlation, cross-correlation, pattern recognition,curve fitting, statistical analysis, and/or other techniques forcomparison. In some cases, one or more parameters of the measurementscan be compared to historical data, such as zero crossing, averages,variances, residuals, standard deviations, maximums, minimums, range,mode, rate of change, etc. Other statistical methods can also beperformed, including p-tests, t-tests, Chi Square, etc.

In some cases, a Host and/or Remote Monitor can select measurements inoverlays and/or historical data sets and be able to see the context inwhich those measurements were taken (e.g., by viewing a log such as Log1100 illustrated in FIG. 11 and/or any other way of displaying any datadiscussed in this disclosure). Such context can allow the Host and/orRemote Monitors to learn from previous experiences and understand whattreatments, or set of circumstances, allowed for good outcomes or badoutcomes. In some implementations, selections can be made on the displayof, and/or communicatively and/or operatively coupled to, a hostmonitoring device, server, and/or remote monitoring device.

In some cases, it may be desirable for a Host and/or Remote Monitor tosee a comparable situation where the Host's analyte measurements, suchas glucose levels, had a similar pattern, and/or to see what the outcomewas. It should be understood that similar displays, functionality,systems, and/or methods in FIGS. 13A-D can also be applied to a RemoteMonitor where analyte measurements of a Remote Monitor are displayed. Inthe case of glucose levels, FIG. 13A illustrates an example comparativecase where a Host had a substantially similarly high glucose reading butended up returning to a normal range relatively quickly. Display 1314includes Graph 1012, Point 1010, Upper Threshold 1016, and LowerThreshold 1018, as were described with reference to FIG. 10. Graph 1312includes historical data with a similar pattern to Graph 1012, in whichthe glucose levels of the historical data initially rise to asubstantially similar high point as Graph 1012, but then decreases belowUpper Threshold 1016 back into a normal range.

Graph 1312 can be identified by pattern recognition. By way ofillustrative example, a host monitoring device, remote monitoringdevice, server, other device, and/or any device discussed in thisdisclosure could look at one or more factors/criteria such as themaximum, the minimum, the time, and the rate of change (e.g., the slopeor derivative), approximate equation for the curve, and/or othersimilarities to identify Graph 1312 as being similar to Graph 1012. Byway of illustrative example, Point 1010 of Graph 1012 and Point 1310 ofGraph 1312, which are both maximums over the range of measurements, havesubstantially similar values. Similarly, the rising slopes (e.g., themeasurements as shown in Display 1314 of Graphs 1012, 1312 between UpperThreshold 1016 and Lower Threshold 1018) are substantially similar.These graphs also appear around the same time and over the same lengthof time. Based on one or more of these factors, a host monitoringdevice, remote monitoring device, server, other device, and/or anydevice described in this disclosure can also look at other measurementsin a database of historical measurements to identify which measurementsets are similar and could be of interest. In some cases, a scoringmethod can be used to determine which measurement sets have the mostsimilarities, such as computing a percentage similarity of each factorand computing an overall metric that is based on those percentages(e.g., in some cases an average of the percentages can be used). In somecases, a user can select criteria (e.g., maximum, minimum, time, andrate of change, approximate equation for the curve, and/or otherfactors) in which to search for comparable data. For example, a user(e.g., Host and/or Remote Monitor) can select options that allow it tolook for a pattern where measurements had a substantially similar highpoint. That user can also search based on dates and times. In somecases, measurements from a different point in time can be transposedand/or overlaid onto a present graph (or the measurements can be viewedin a non-graphical representation) to see similarities between thosemeasurements and recent measurements.

In some cases, a Host and/or Remote Monitor can desire to viewhistorical data measurements that had a poor outcome for the Host. Forexample, a Host and/or Remote Monitor can be interested in seeing asituation where the Host had a hyperglycemic reaction as a point tocompare recent measurements.

FIG. 13B illustrates a comparative case where the Host was not able tocontrol glucose levels and went into a hyperglycemic state. Display 1324shows Graph 1012 and Graph 1322. While Graph 1012 rises and then turnsdownward towards Point 1008, Graph 1322 continues to rise to Point 1328.In some cases, by comparing Graph 1322 and Graph 1012, and/or any logsand/or other data giving the measurements of Graph 1322 and/or Graph1012 context, a Host and/or Remote Monitor can learn why the Host'sglucose level kept going up in Graph 1322 and what can be done toprevent the same thing from happening.

FIG. 13C illustrates a comparative case where the Host was able to keepglucose levels within the predefined range. Display 1334 again displaysGraph 1012. Display 1334 also displays Graph 1332, which reflects asituation where the Host maintained his/her glucose measurements betweenUpper Threshold 1016 and Lower Threshold 1018. In some cases, bycomparing Graph 1332 and Graph 1012, and any logs or other data givingthe measurements of Graph 1332 and Graph 1012 context, a Host, RemoteMonitor, and/or processor (e.g., a processor of a host monitoringdevice, remote monitoring device, and/or server using patternrecognition) can learn why the Host's glucose level stayed within UpperThreshold 1016 and Lower Threshold 1018 in Graph 1332, and what can bedone to control glucose levels in the future.

FIG. 13D illustrates a curve of average values in similar circumstances,where a confidence interval is also displayed. In some cases, it may bedesirable to view other kinds of statistics and/or parameters forcomparison. For example, a Host's average glucose measurements at adetermined time of day (and/or range of times), during determinedactivities, in determined ranges, during determined events (e.g.,eating), and/or using any characteristics desired can be viewed. Display1344 again displays Graph 1012. Display 1344 can also display Graph1342, which can include average glucose measurements of the Host insimilar time periods. Other statistics can also be displayed in additionor in the alternative to averages, such as variances, standarddeviations, confidence intervals, maximums, minimums, range, mode, rateof change, etc. Graph 1342 also includes confidence intervals. By way ofillustrative example, Graph 1342 includes Point 1346, which can be anaverage over a determined period of time. Graph 1342 can also display95% percent confidence interval with Upper Bound 1348 and Lower Bound1350 around Point 1346, allowing for further understanding of a Host'smeasurements.

Furthermore, in some implementations, a Host and/or Remote Monitor maynot be interested in recent measurements at all, and/or desire toreflect on previous, historical occurrences. As such, using similarcomparisons and factors as described above, with respect to any of FIGS.13A-D, a remote monitoring device (e.g., Remote Monitoring Device 300),host monitoring device (e.g., Host Monitoring Device 200), server (e.g.,Secure Server 504), and/or any other device described in this disclosurecan view two or more historical measurement sets.

In some cases, it may be desirable for Hosts and/or Remote Monitors tobe able to adaptively and contextually modify what kinds ofcommunications can be sent between Hosts and Remote Monitors. Byallowing such modification, monitoring systems can enhance Host andRemote Monitor relationships and assist in allowing the right amount andkinds of information (e.g., not too much or too little) to transfer froma Host to each of his/her Remote Monitors.

A remote monitoring device (e.g., Remote Monitoring Device 300), hostmonitoring device (e.g., Host Monitoring Device 200), server (e.g.,Secure Server 504), and/or any other device described in this disclosurecan provide adaptive and/or contextual communication of a Host based ona Host's activities, measurements, and/or other data (e.g., analytemeasurements, communications, Processed Data, Contextual Data, HealthData, System Data, Treatment Data, User Data, Sensor Data, and/or anydata described in this disclosure). Similarly, such adaptive and/orcontextual communication can be based on a Remote Monitor's activities,classification, and/or other data (e.g., analyte measurements,communications, Processed Data, Contextual Data, Health Data, SystemData, Treatment Data, User Data, Sensor Data, and/or any data describedin this disclosure), and/or patterns in such data.

FIGS. 14A-D illustrate example interactions of different classificationsof Remote Monitors. While FIGS. 14A-D reference Remote Monitors (e.g.,Remote Monitors 1410, 1412, 1414, 1416) and a Host, it should beunderstood that each Remote Monitor has a remote monitoring device andeach Host has a host monitoring device. A remote monitoring device canbe substantially similar to Remote Monitoring Device 300 and/or performprocesses substantially similar to Process 150. A host monitoring devicecan be configured substantially similar to the Host Monitoring Device200 and/or can perform processes substantially similar to Process 100.Such remote monitoring devices and host monitoring device can sendand/or receive communications, determine classifications, and/or operatebased on classifications as will be described. Classifications can bestored in memory in one or more of the host monitoring devices, remotemonitoring devices, servers, and/or other devices. Similarly,classifications can be determined, for example, by a processor of a hostmonitoring device, remote monitoring device, server, and/or otherdevices. For example, a remote monitoring device can determine its ownclassification and store it in memory. The remote monitoring device canalso store in memory the classification of other remote monitoringdevices. Advantageously, this can allow the remote monitoring device toknow how to communicate (e.g., with notifications, alerts, messages,data, and/or any other communications in this disclosure) with otherremote monitoring devices and/or its relative role as compared to otherremote monitoring devices in its monitoring system. Similarly, a hostmonitoring device and/or a server (e.g., secure server) can store inmemory the classifications of one or more or all of its Remote Monitors.Advantageously, for example, this can allow the host monitoring deviceto know the relative relationship the Host has with the Remote Monitorsin its system, and/or send communications based on classifications andpermissions attributed to Remote Monitors. Also, in someimplementations, a server (e.g., a secure server) can store theclassifications of the Remote Monitors in order to direct communicationsto the relevant Remote Monitors. In this way, the server can act as anintelligent central hub(s) that can direct communication traffic in theremote monitoring system by, for example, storing, receiving and/orsending.

In some embodiments, each classification is associated with a set ofpermissions, which can determine what data a remote monitoring devicecorresponding to a classification is authorized to access. The set ofpermissions can be pre-selected and/or modifiable by Host for eachremote monitoring device.

FIG. 14A illustrates that, in some cases, monitoring systems can haveclassifications that create a hierarchical structure wherecommunications from a Host first go to higher classified Remote Monitorsbefore passing to lower classified Remote Monitors. In some embodiments,the lower classified Remote Monitors can have greater restrictions tothe permissible data that they can access compared to the higherclassified Remote Monitors. In some cases, the lower classified RemoteMonitors can have more restrictive notification rules compared withhigher classified Remote Monitors. Having such classifications can allowsome Remote Monitors not to be inundated with information that they donot desire to see and/or would not be helpful for them to see. Also, asdescribed herein, Remote Monitors may not desire to see alerts when theyhave already been addressed.

In some cases, Remote Monitors can be assigned classifications based onone or more of the following: proximity between a host device and aremote monitoring device, a characteristic of the user of the remotemonitoring device communicated to a secure server managing the remotemonitoring system, a relationship between the user of the remotemonitoring device and Host, and/or a behavior of a remote monitoringdevice.

For example, in the case where Remote Monitors 1410, 1412, 1414, 1416are all Caretakers of a Host. Remote Monitors 1410, 1412, 1414, 1416 canbe divided into Primary Classification 1404, Secondary Classification1406, and Tertiary Classification 1408 of the Caretaker classification.As illustrated, Remote Monitor 1410 is in Primary Classification 1404.Remote Monitors 1412, 1414 are in Secondary Classification 1406. AndRemote Monitor 1416 is in Tertiary Classification 1408. In some casesPrimary Classification 1404, Secondary Classification 1406, and TertiaryClassification 1408 can define relative roles with respect to RemoteMonitors and the Host. More classifications can be made to furtherdefine roles (e.g., quaternary, quinary, senary, and so forth, or anyother name or designation desired). For example, Remote Monitors inPrimary Classification 1404 can be the persons directly taking care of aHost. By way of illustrative example, where a Host is a child,Caretakers in Primary Classification 1404 can be the child's parent inclose proximity. Such Caretaker Remote Monitors in PrimaryClassification 1404 can be the ones presently and/or actively takingcare of the child. The Host child can also have other Caretakers. Forexample, Caretaker Remote Monitors in Secondary Classification 1406 canbe the child's other parent or grandparent who are not in closeproximity. These Caretaker Remote Monitors in Secondary Classification1406 can have an interest in the Host (e.g., when Host is a child) andwould take care of the Host in his/her presence, but are presently away.These Caretaker Remote Monitors in Secondary Classification 1406 can beinterested in what is happening with Host, but may not be in a positionto assist Host unless the Caretaker in Primary Classification 1404 didnot or was unable to respond to an emergency. Accordingly, theseCaretaker Remote Monitors in Secondary Classification 1406 may not needall the communications. Accordingly, Remote Monitors of SecondaryClassification 1406 may have more restrictive notification rulescompared with Remote Monitors of the Primary Classification 1404.Similarly, Caretaker Remote Monitors in Tertiary Classification can beeven further removed, such as an aunt or uncle who have an interest inthe child Host, but would desire to step in if Caretaker Remote Monitorsin Primary Classification 1404 and Secondary Classification 1406 did notor were unable, or if there was an emergency.

In some embodiments, Remote Monitors can be assigned to one or moreclassifications generated and managed at a server as described herein.The classifications may include varying notification rules. The servercan receive the location of a remote monitoring device and modify theclassification of a remote monitoring device based on a predefinedproximity from a host device. In some embodiments, the modification ofclassification may include relegating a remote monitor from a higherprivilege/priority classification to a lower privilege/priorityclassification based on proximity.

In some embodiments, the classification may be relegated from a higherprivilege/priority classification to a lower privilege/priorityclassification based on status or availability of the user of a remotemonitoring device.

Other roles of classifications can be defined as desired by Hosts,Remote Monitors, Administrators, practitioners, operators, etc. PrimaryClassification 1404, Secondary Classification 1406, Tertiary 1408, andany other classification can apply to other roles, and not justCaretakers. For example, substantially similar hierarchies can beapplied to Social Associates, Strangers, Watchers, Assigned RemoteMonitors, Universal Remote Monitors, and/or any other Remote Monitordescribed in this disclosure.

As a result of the hierarchy, not all communications from a Host's hostmonitoring device, such as Communication 1402, may go to remotemonitoring devices of all Remote Monitors (e.g., Remote Monitors 1410,1412, 1414, 1416). For example, a remote monitoring device may not sendall communications to the remote monitoring devices in its remotemonitoring system. As another non-limiting example, a host monitoringdevice can send a communication to a server, and the server may notdirect the communication to all remote monitoring devices in themonitoring system.

By way of illustrative example, Communication 1402 can first go to aremote monitoring device of Remote Monitor 1410 in PrimaryClassification 1404. In the case where the contents of Communication1402 can be addressed by Remote Monitor 1410, Communication 1402 may notgo to remote monitoring devices of Remote Monitors (Remote Monitors1412, 1414, 1416) or may be altered before being sent.

For example, Communication 1402 can be an alert message, stating thatHost's glucose level is low. Communication 1402 can be sent to a remotemonitoring device of Remote Monitor 1410 in Primary Classification 1404.The Remote Monitor 1410 can address the alert by making sure Host eatsan appropriate food. As a result of Remote Monitor's actions, it may notbe desirable to further alert Remote Monitors 1412, 1414, 1416 and/orsend the same alert to their remote monitoring devices.

In some implementations a remote monitoring device (e.g., RemoteMonitoring Device 300), host monitoring device (e.g., Host MonitoringDevice 200), server (e.g., Secure Server 504), and/or other devicesdescribed in this disclosure can have a delay before transmitting alertsor notifications (e.g., 30 minutes or other desirable delay as describedherein). If the reason for which Communication 1402 is to be sent hasbeen addressed, the alert may not be sent to remote monitoring devicesof one or more of Remote Monitors 1412, 1414, 1416. For example, noalert may be sent at all, or a lower level alert and/or notificationstating the issue and/or that the issue has been addressed can be sent.Whether or not an issue has been addressed can be determined from Hostinput (e.g., Host indicating a meal has been taken), analytemeasurements, Processed Data, communications from Host or RemoteMonitor, Contextual Data, Health Data, System Data, Treatment Data, UserData, Sensor Data, Summary Data, and/or other data as described herein.

In some implementations, Remote Monitor 1410, after receivingCommunication 1402 with a remote monitoring device, can preventCommunication 1402 from being sent to one or more of Remote Monitors1410, 1412, 1414, 1416 (e.g., at their remote monitoring devices) byacknowledging Communication 1402, sending a message, and/or any otherform of communication indicative of Remote Monitor 1410 seeingCommunication 1402 and/or addressing the situation. In some cases, suchacknowledgment, sending a message, and/or any other form ofcommunication can be in the form of a response inputted by the RemoteMonitor on a user interface that displays Communication 1402. In suchcases, a host monitoring device may not send Communication 1402 to oneor more of Remote Monitors 1410, 1412, 1414, 1416. In other situations,Remote Monitor 1410 can select a response to Communication 1402 thatsends Communication 1402 to one or more of Remote Monitors 1410, 1412,1414, 1416. For example, there could be a response that allows RemoteMonitor 1410 to select one or more Remote Monitors 1410, 1412, 1414,1416 to receive the message. As another non-limiting example, RemoteMonitor 1410 can send an ignore or “I'm busy” response (e.g., byselecting an option in a pulldown menu and/or hitting an on-screenbutton in a display). Communication 1402 can then cascade (e.g., besent) to the remote monitoring devices of the next classification in thehierarchy, which can be Remote Monitors in Secondary Classification 1406in this case.

In some cases, where Remote Monitor 1410 has not addressed a situation,has not acknowledged Communication 1402, and/or a delay has expired,Communication 1402 can be sent in whole or in part to other RemoteMonitors. A host monitoring device, server, and/or other devicedescribed in this disclosure can perform such sending. By way ofillustration, in the example hierarchical structure illustrated in FIG.14A, Communication 1402 may then be sent (e.g., from a host monitoringdevice) to Remote Monitors 1412, 1414 because they are in the nextclassification in the hierarchy, Secondary Classification 1406.

In some implementations, the same process just described can filter downthroughout the classifications. For example, remote monitoring devicesof Remote Monitors 1412, 1414 in Secondary Classification 1406 canreceive a communication (e.g., Communication 1402 or a communicationbased on Communication 1402 after Remote Monitor 1410 has seen it). Ifone or more of Remote Monitors 1412, 1414 address a situation within adelay period, then the same alert may not be sent to remote monitoringdevices of Remote Monitors in Tertiary Classification 1408, such asRemote Monitor 1416. In some implementations, one or more RemoteMonitors 1412, 1414, after receiving the communication, can prevent thatcommunication from being sent to Remote Monitor 1416 by acknowledgingthat communication, sending a message, and/or any other form ofcommunication indicative of one or more of Remote Monitors 1412, 1414seeing the communication and/or addressing the situation. In some cases,such acknowledgment, sending a message, and/or any other form ofcommunication can be in the form of a response inputted by the RemoteMonitor on a user interface that displays the communication. In somecases, where Remote Monitors 1412, 1414 have not addressed a situation,have not acknowledged the communication, and/or a delay has expired, thecommunication (e.g., Communication 1402 and/or a communication based onCommunication 1402 after Remote Monitor 1410 has seen it) can be sent inwhole or in part to remote monitoring devices of Remote Monitors inTertiary Classification 1408. A host monitoring device, server, and/orany other device described in this disclosure can perform such sending.The aforementioned pattern can continue for more classifications. Itshould be noted that in some implementations, one or moreclassifications may not contain a Remote Monitor. In such a case,messages can be sent to Remote Monitors based on their relativeclassifications, not their absolute. For example, if there are no RemoteMonitors in Primary Classification 1404, Communication 1402 can first besent to Remote Monitors in Secondary Classification 1406 and so forth.In some cases, a processor (e.g., a processor of a host monitoringdevice, remote monitoring device, server, and/or any other devicedescribed in this disclosure) can assign classifications so thatclassifications are filled from primary on down with no emptyclassifications.

In some implementations, it can be desirable for Remote Monitors tochange classifications dynamically in order to account for RemoteMonitor and/or Host conditions and Remote Monitor's ability to assist aHost.

FIG. 14B illustrates that classifications can be dynamic, where theclassification of a Remote Monitor can be based on Host and/or RemoteMonitor preferences and/or data acquired on a Remote Monitor. Forexample, Remote Monitor 1410 was illustrated as part of the PrimaryClassification in FIG. 14A, but is shown as in Tertiary Classification1408 in FIG. 14B. Similarly, Remote Monitor 1412 was previously inSecondary Classification 1406, but is now illustrated in PrimaryClassification 1404. Such changes can dynamically occur based on factorssuch as location of the Remote Monitor and/or Host, data about the Hostand/or Remote Monitor (e.g., analyte measurements, communications,Processed Data, Contextual Data, Health Data, System Data, TreatmentData, User Data, Sensor Data, Summary Data, and/or any data described inthis disclosure), preferences (e.g., preferences and/or desires ofHosts, Remote Monitors, practitioners, and/or any other person),frequency and/or quality of communication responses, and/or any otherfactor or criteria desirable. These dynamic changes can be analyzedand/or processed a remote monitoring device (e.g., Remote MonitoringDevice 300), host monitoring device (e.g., Host Monitoring Device 200),server (e.g., Secure Server 504), and other devices. In some cases,changes in classifications can be made automatically. In some cases,changes in classifications may first be detected, and then prompted on aremote monitoring device and/or host monitoring device. If such changein classification is approved by the user of the prompted remotemonitoring device and/or host monitoring device (e.g., by a Host and/orRemote Monitor responding and/or clicking an approve button), then thechange can be made. If such change in classification is declined by theuser of the prompted remote monitoring device and/or host monitoringdevice (e.g., by a Host and/or Remote Monitor responding and/or clickinga decline button), then the change may not be made. Changes inclassifications can be made in memory of a host monitoring device,remote monitoring device, server, and/or any other device described inthis disclosure.

For example, a Remote Monitor can change classifications based onlocation, such as proximity of Remote Monitors and/or Hosts. RemoteMonitor 1410 could have been in Primary Classification 1404 when RemoteMonitor 1410 was in close proximity (e.g., between 0 and 1,045 squaremeters and/or within a suitable range to see, hear, and/or otherwisetake care of a Host and/or the closest Remote Monitor to the Host).However, when Remote Monitor 1410 is not in close proximity, RemoteMonitor 1410 may be a different classification, such as TertiaryClassification 1408. Other factors can be considered in addition or inthe alternative to proximity. As another non-limiting example, theavailability of a Remote Monitor can be taken into account indetermining classification. Data (e.g., analyte measurements,communications, Processed Data, Contextual Data, Health Data, SystemData, Treatment Data, User Data, Sensor Data, Summary Data, and/or anydata described in this disclosure) can be indicative of availability.For example, where a Remote Monitor is wearing a GCM, if the RemoteMonitor has a hyperglycemic or hypoglycemic condition (or otherwisedetermined glucose conditions that are not desirable), then that RemoteMonitor may not be in a position to be available to assist a Host. Otherhealth-related factors indicative of a Remote Monitor's availabilityinclude, high/low heart rate, high/low temperatures, sleep (e.g., asdetermined by a sleep monitor or accelerometer), high levels of anxiety,high/low blood pressure, high/low ratings on a worry scale, etc.

Dynamic changes of Remote Monitor classification can happen byconsideration of the aforementioned factors by a remote monitoringdevice (e.g., Remote Monitoring Device 300), host monitoring device(e.g., Host Monitoring Device 200), server (e.g., Secure Server 504),and/or any other device described in this disclosure. In some cases,changes can be user-inputted, such as by a Host and/or Remote Monitorassigning Remote Monitors to classifications.

FIG. 14C illustrates an example where Remote Monitors (e.g., usingremote monitoring devices), can communicate with each other and/orexchange data and/or information. In some cases, communications from aHost can be relayed between Remote Monitors at their remote monitoringdevices. In some cases, each remote monitoring device can store inmemory its classification and the classifications of one or more remotemonitoring devices in its monitoring system. Advantageously, suchstorage can allow each remote monitoring device to determine whatcommunications to send to other remote monitoring device, and/or whatcommunications to display. In some implementations, a server (e.g.,Secure Server 504) can store the classifications and/or synchronize(e.g., send updates) to the remote monitoring devices so that they haveupdated information on the classifications of other remote monitoringdevices in their monitoring system.

By way of illustrative example, Communication 1464 can be sent to RemoteMonitor 1410, who for illustrative purposes, can be in PrimaryClassification 1404. As described with reference to FIG. 14A, RemoteMonitor 1410 can take actions such as addressing the contents ofCommunication 1464 (e.g., addressing the issue of which Communication1464 is about), acknowledging Communication 1464, sending a message,and/or any other form of communication. In such cases, acknowledgments,sending of messages, and/or any other form of communications can be inthe form of a response inputted by the Remote Monitor on a userinterface. Where such action is taken, Communication 1464 may not berelayed to Remote Monitors 1412, 1414, 1416. Instead, no communicationcan be sent, or another communication (e.g., an alert, notification,message, or other communication) can be generated by Remote Monitor 1410(e.g., using a remote monitoring) to send to other Remote Monitors, suchas Remote Monitors 1412, 1414 in Secondary Classification 1406. Suchother communication can be based on the classes of one or more of RemoteMonitor 1410, 1412, 1414, 1416, Communication 1464, the actions taken byRemote Monitor 1410, responses by Remote Monitor 1410, and/or other dataand/or information. For example, where Remote Monitor 1410 took actionsthat address the content of Communication 1464 (e.g., whereCommunication 1464 was an alert stating low glucose and Remote Monitor1410 feeding Host), communications to Remote Monitors 1412, 1414 can benotifications that say Host's glucose was low and Remote Monitor 1410addressed it. Such notification can be displayed on a user interface ofthe remote monitoring devices of Remote Monitors 1412, 1414. In the casewhere Remote Monitor 1410 does not take actions to address Communication1464 and/or a delay has expired, Communication 1464 may automaticallypass to one or more of Remote Monitors 1412, 1414, 1416. A similarinteraction can occur between Remote Monitors 1412, 1414, whereunaddressed communications pass to Remote Monitors 1416, or where thecommunications are addressed, no communication is sent or anothercommunication is sent from remote monitoring devices of Remote Monitors1412, 1414. Such other communication can be based on the classes of oneor more of Remote Monitor 1410, 1412, 1414, 1416, Communication 1464,responses to communications, the communication received by RemoteMonitors 1412, 1414, the actions taken by Remote Monitors 1412, 1414,and/or other data and/or information.

In other situations, Remote Monitors can select to send Communication1464 or other communications to one or more other Remote Monitors. Forexample, there can be a response to Communication 1464 and/or othercommunications that allows Remote Monitor 1410 to select one or moreother Remote Monitors to receive the message. In some cases, a RemoteMonitor can send an ignore or “I'm busy” response, and the communicationcan cascade (e.g., be sent) to the next classification in the hierarchyand/or other classifications. In some cases, permissible communicationscan cascade to other Remote Monitors who would not have otherwisereceived that information.

Furthermore, each of Remote Monitors 1410, 1412, 1414, 1416 cancommunicate with one another using communication channels between theirremote monitoring devices, such as Channel 1462. Such communication canenable a higher level of coordination and care of a Host from RemoteMonitors. For example, Remote Monitors 1412, 1414, 1416 can communicatewith Remote Monitor 1410, who can be in Primary Classification 1404, togive Remote Monitor 1410 feedback, requests, directions, data, etc.Moreover, Remote Monitor 1410 can give Remote Monitors 1412, 1414, 1416updates, information, requests, feedback, directions, data etc. In someimplementations, Communication 1402, which can be sent from a hostmonitoring device, can also be sent to one or more of Remote Monitors1412, 1414, 1416.

In addition, or in the alternative, in some implementations, the samecommunication can be sent and/or relayed to a plurality of RemoteMonitors. However, the remote monitoring devices of the plurality ofRemote Monitors can have different displays in response to thecommunication based on the classification of the receiving RemoteMonitor. For example, a remote monitoring device of a Remote Monitor inPrimary Classification 1404 can receive a communication and displaysubstantially all of the communication including a data measurement andan alert, whereas a remote monitoring device of a Remote Monitor inSecondary Classification 1406 may only display a data measurement.

FIG. 14D illustrates an example discussion chain between RemoteMonitors, in which the Remote Monitors can share information about aHost and/or any other information the Remote Monitors want to shareand/or discuss. Discussion chains (e.g., logs) can be restricted or openbased on individual Remote Monitors, classifications of Remote Monitors,urgency, proximity of the Host and/or Remote Monitors, etc. RemoteMonitors can be identified (e.g., by name, remote monitoring deviceserial number, nickname, classification, etc.) or anonymous. Discussion1470 shows a plurality of Remote Monitors discussing a Hosts' glucosemeasurements. Each Remote Monitor can see the other's messages, whichcan allow them to coordinate care. However, in some implementations,only some Remote Monitors may see some messages, and only other RemoteMonitors may see other messages. Discussion 1470 can be displayed on aremote monitoring device (e.g., Remote Monitoring Device 300), hostmonitoring device (e.g., Host Monitoring Device 200), server (e.g.,Secure Server 504), and/or any other device described in thisdisclosure. Advantageously, a remote monitoring device can viewDiscussion 1470 to see what its Remote Monitors are discussing and/orother Remote Monitors are discussing. Similarly, a host monitoringdevice can view Discussion 1470 in order to see what its Remote Monitorsare discussing. A server can store Discussion 1470 in memory and/ordisplay Discussion 1470 on a display communicatively and/or operativelycoupled to the server. In some implementations, the server cancoordinate and/or compile the communications into Discussion 1470.

In some implementations, the monitoring system can include a server anda plurality of remote monitoring devices. The plurality of remotemonitoring devices can each have a classification. Each of the pluralityof remote monitoring devices can be configured to send communications tothe server. The server can be configured to create a log (e.g.,Discussion 1470) containing a subset of the communications between theplurality of remote monitoring devices and the server. The creation ofthe log can be based on the classification of the communicating remotemonitoring device. The server can then send the log to the remotemonitoring devices whose communications are included in the log. In someimplementations, the server can also send the log to a host monitoringdevice. In some implementations, the communications from one or moreremote monitoring devices can be restricted out of the log.

FIG. 15 illustrates an example classification of Remote Monitors wheredifferent classifications of Remote Monitors receive different amountsand/or different kinds of data. Whereas FIG. 14A-C showed hierarchicalstratification of classes, FIG. 15 illustrates lateral stratification.Classifications can have both hierarchical (or vertical) and lateralstratification (e.g., Watchers, Caretakers, Social Associates, etc. canhave Primary, Secondary, Tertiary, etc. classifications). In lateralstratification, the different classes (e.g., Caretakers, SocialAssociates, Strangers, Watchers, Assigned Remote Monitors, UniversalRemote Monitors, etc.) receive different kinds and different amounts ofdata. Such classifications can also be stored in memory and/ordetermined by a remote monitoring device, host monitoring device,server, and/or any other device described in this disclosure.

In some embodiments, the server may provide a message informative of anevent associated with the analyte state of a Host to a Remote Monitorhaving a higher privilege/priority classification. If the Remote Monitorfails to provide an acknowledgement response to the message, within apredetermined time period, the server can relegate the Remote Monitor'sclassification to a different, for example, a lower privilege/priorityclassification. In some embodiments, the server may send a plurality ofmessages informative of an event associated with the analyte state ofHost. The relegating can occur after a predetermined number of instancesof lack of acknowledgement from Remote Monitor.

In addition, the server may elevate the classification of the RemoteMonitor to a different classification, for example, from a lowerprivilege/priority to a higher one based on receipt of acknowledgementresponse from the Remote Monitor, within a predetermined period of time.In some embodiments, when a plurality of messages informative of Hoststate has been sent, the elevating can occur after receipt of apredetermined number of instances of acknowledgement responses.

In some cases, the server can provide an alert informative of an eventassociated with the analyte state of the host to a first remotemonitoring device in a first classification, based on the notificationrules associated with the first classification. The server can receive aresponse from the first remote monitoring device indicative of inabilityor unavailability of a Remote Monitor to react to the alert.Alternatively, the sever may detect a lack of response from the firstremote monitoring device within a predetermined time period afterproviding the alert. The server can provide the alert to a secondmonitoring device. In some embodiments, the server may send the alert toa second remote monitoring device when the Remote Monitor associatedwith the first remote monitoring device indicates an ability to react tothe alert. In some embodiments, the classification of the second remotemonitoring device can be elevated after receiving an acknowledgementwithin a predetermined time after providing the alert to the secondmonitoring device. In some embodiments, the classification of a firstremote monitoring device can be relegated to a lower privilege/priorityclassification based on lack of response or receiving of a messageindicating inability or unavailability of the Remote Monitor associatedwith the first remote monitoring device.

In some embodiments, the notification rules associated with a givenclassification may be overridden before providing an alert to a secondremote monitoring device, where the classification may otherwise notallow for delivery or receipt of the alert. The overriding may alsooccur based on the severity factor of the information associated withthe alert.

Remote Monitor 1510, who can be in Caregiver Classification 1504, canreceive with a remote monitoring device Communication 1524.Communication 1524 can include notifications, messages, and/or alertsregarding a Host's analyte measurements (e.g., glucose level) and/ordata based on other data (e.g., Processed Data, Contextual Data, HealthData, System Data, Treatment Data, User Data, Sensor Data, Summary Data,and/or any data described in this disclosure). A high degree ofcommunication can be helpful to Remote Monitor 1510 as a Caretaker.

Remote Monitor 1514 can be in Watcher Classification 1506. As a Watcher,Remote Monitor 1514 may have less responsibility as to the Host than aCaretaker, and may not desire as much communications. As suchCommunication 1526 can contain less information, and may not contain thedetail that a Caretaker may desire. Communications can also be sent to aremote monitoring device of Remote Monitor 1514 less frequently.

Remote Monitors 1512, 1516 can be in Social Classification 1508. AsSocial Associates, Remote Monitors 1512, 1516 may have little to noresponsibility for the Host, and may not desire much communication atall besides high-level data. As such Communication 1528 can contain evenless information than Communication 1526, and may not contain the detailthat a Caretaker or Watcher may desire. Communications can also be sentto remote monitoring devices of Remote Monitors 1512, 1516 lessfrequently.

In some implementations, communications can be relayed between RemoteMonitors in different classifications (e.g., Caretaker Classification1504, Watcher Classification 1506, and Social Classification 1508) wherea remote monitoring device of a first Remote Monitor in a first classreceives a communication, and then sends a different communication to aremote monitoring device of a second Remote Monitor in a second class.In some cases, the different communication can include less data and/orinformation. For example, if the first Remote Monitor is a Caretaker andthe second Remote Monitor is a Social Associate, the Social Associatemay desire less information than the Caretaker. Such differentcommunication can be based on the communication of the first class, theclasses of the first and second Remote Monitors, actions of the firstRemote Monitor, and/or any other criteria desired. By way ofillustrative example, Remote Monitor 1510 can receive at a remotemonitoring device Communication 1524, which can contain a low glucosemeasurement and an alert. As a Caretaker, Remote Monitor 1510 can thenfeed the Host. Remote Monitor 1510's remote monitoring device can thengenerate a communication to send to a remote monitoring device of RemoteMonitor 1514, who is in Watcher Classification 1506, that says theHost's low glucose measurement and that Remote Monitor 1510 fed theHost. Since Remote Monitor 1514 may desire less information than aCaretaker, Remote Monitor 1514 may receive less information, such as alog update and/or a low priority notification. Had Remote Monitor 1514been in Caretaker Classification 1504, he/she may have received moreinformation, such as a message and/or a higher priority notification.

In some embodiments, a first Remote Monitor in one classification cansend a request to elevate a second Remote Monitor to a higherprivilege/priority classification. In some embodiment, the elevatingoccurs after the second Remote Monitor has indicated acceptance of thehigher privileges and duties associated with the higher classification.

In some implementations, a communication can be sent and/or relayed to aplurality of Remote Monitors. However, the remote monitoring devices ofthe plurality of Remote Monitors can have different displays in responseto the communication based on the classification of the receiving RemoteMonitor. For example, a Caretaker can receive a communication anddisplay substantially all of the communication including a datameasurement and an alert, whereas a remote monitoring device of a SocialAssociate may only display a data measurement.

In some cases, it can be desirable to have a way to assign aclassification to each Remote Monitor. In some implementations, a userinterface can allow a Host and/or Remote Monitor to assign aclassification to a Remote Monitor, and/or allow a Host and/or RemoteMonitor to customize the communications and/or other data received by aparticular Remote Monitor. The notification rules can definecircumstances to send a message to a respective remote monitoring deviceinformative of an event associated with the analyte state of the Host.The notification rules can be modifiable by the authorized remotemonitoring devices within the scope of a set of permissions to the dataassociated with the respective remote monitoring device.

In some embodiments, the permissible data can include (i) retrospectivesensor data, (ii) real time sensor data, and (iii) a trend in the rateof change of the analyte state of the host, as well as other types ofdata described herein.

FIGS. 16A-D illustrate an example display allowing the selection of aclassification for a Remote Monitor and configuration of other settings.The display can be displayed on a host monitoring device that isfollowed by remote monitoring devices. In some cases, the contents ofthe display can be stored on a server (e.g., Secure Server 504). In someimplementations, the classification of Remote Monitor can be selectedand preferences automatically filled in. In addition or in thealternative, for each individual Remote Monitor, a Host, Remote Monitor,Administrator (e.g., adult caretaker of a child host, such as aparent/guardian or health care provider), and/or other user can definethe frequency of communications, rights, and/or privileges of thatRemote Monitor.

In some cases, it may be desirable to be able to quickly configure anyRemote Monitor, including newly added Remote Monitors. Pull-down Menu1602 can be used to select from the group of predefinedclassifications/classes, and/or any classification described in thisdisclosure (e.g., Caretakers, Social Associates, Strangers, Watchers,Assigned Remote Monitors, Universal Remote Monitors, and/or any otherrole, and/or their hierarchical classification, including Primary,Secondary, Tertiary, and the like). The Pull-down Menu 1602 can also beused to define any user-defined class as desired. If such is selected,the frequency of communications, rights, and/or privileges of a RemoteMonitor can be predefined in one or more sets of permissions and/or inone or more sets of notification rules. In some cases, a particularRemote Monitor can be restricted in the classifications/classes thathe/she can choose. In a non-limiting example, a Remote Monitor may bepresented with the display of FIG. 16A on his/her remote monitoringdevice, and/or wish to be a Primary Caretaker. However, if the Hostand/or an Administrator has restricted that Remote Monitor from being aPrimary Caretaker, then the Caretaker may only be presented withavailable choices based on the restriction, such as “SecondaryCaretaker” and/or “Tertiary Caretaker” or the like, on the Pull-downMenu 1602.

In some cases, a Remote Monitor, Host, and/or other user may desire todefine (e.g., customize) the settings for a particular individual.Returning to FIG. 16A, as a non-limiting example, such Remote Monitor,Host, Administrator, and/or other user can use a user interface todefine such settings. For example, Cell 1604 can define how the RemoteMonitor receives Urgent Low Alerts (e.g., urgent alerts when a Host'sglucose level is low). Such Urgent Low Alerts can be toggled on/offusing Slide 1606. The Remote Monitor, Host, and/or other user can setThreshold 1608, in which, when glucose measurements of the Host with ahost monitoring device are less than or equal to Threshold 1608, analert can occur. Alert Type 1610 can be used to set how an alert occurs,such as a sound, vibration, flashing light, etc.

Similarly, Cell 1612 can define how the Remote Monitor receives LowAlerts (e.g., alerts when a Host's glucose level is low). Such LowAlerts can be toggled on/off using Slide 1614. The Remote Monitor, Host,and/or other user can set Threshold 1616, in which, when glucosemeasurements of the Host with a host monitoring device (e.g., a hostmonitoring device that can be substantially similar to Host MonitoringDevice 300 and/or any other device described in this disclosure) areless than or equal to Threshold 1616, an alert can occur. Otherthresholds can be set, such as Threshold 1618, which can give a durationof measurements (e.g., greater than or equal to Threshold 1618) that canset off a Low Alert. Threshold 1620 can be used to set an amount ofsnooze before re-alerting.

Similarly, Cell 1622 can define how the Remote Monitor receives HighAlerts (e.g., alerts when a Host's glucose level is high). Such HighAlerts can be toggled on/off using Slide 1624. The Remote Monitor, Host,and/or other user can set Threshold 1626, in which, when glucosemeasurements of the Host with a host monitoring device are greater thanor equal to Threshold 1626, an alert can occur. Other thresholds can beset, such as Threshold 1628, which can give a duration of measurements(e.g., greater than or equal to Threshold 1628) that can set off a HighAlert. Threshold 1630 can be used to set an amount of snooze beforere-alerting. Alert Type 1632 can be used to set how an alert occurs,such as a sound, vibration, flashing light, etc.

Similarly, Cell 1634 can define how the Remote Monitor receives alertswhen no data has been transmitted. Such No Data Alerts can be toggledon/off using Slide 1636. The Remote Monitor, Host, and/or other user canset Threshold 1638, in which, if no data has been received for aduration greater than or equal to Threshold 1638, an alert is sent.Alert Type 1640 can be used to set how an alert occurs, such as a sound,vibration, flashing light, etc. Other types of alerts can be set asdesired.

Other rights, privileges, and/or other settings can be also configuredfor the Remote Monitor. FIG. 16B illustrates more options. Cell 1652 canbe used to set the wait for response (e.g., delay) for a Remote Monitor.Cell 1654 can be used to set whether the Remote Monitor's remotemonitoring device status (e.g., whether or not it is functioningproperly by looking at System Data) will be taken into account incommunicating. Cell 1656 can set whether a Remote Monitor's healthcharacteristics (e.g., based on analyte measurements or other data,including communications, Processed Data, Contextual Data, Health Data,System Data, Treatment Data, User Data, Sensor Data, Summary Data,and/or any data described in this disclosure) will be taken into accountfor communications, and any thresholds to consider when consideringwhether or not to communicate to a Remote Monitor. For example, a RemoteMonitor may not receive communications if his/her glucose measurementsfalls outside of a defined range (e.g., defined by minimum and maximumvalues), his/her heart rate is greater than or equal to a definedthreshold, and/or his/her blood pressure is over a defined threshold. AHost and/or Remote Monitor can similarly set parameters for other healthcharacteristics in which a Remote Monitor will and/or will not getcommunications. In some embodiments, the classification of RemoteMonitor may be modified from a high to low or vice versa, based on thatRemote Monitor's health characteristics relative to other RemoteMonitors.

FIG. 16C illustrates more options. Other rights and/or privileges can beset for a Remote Monitor, such as Cell 1682, which can allow or disallowa Remote Monitor from viewing logs (e.g., Log 1100) associated withglucose measurements. Such may be desirable because certain types ofRemote Monitors (e.g., Caretakers) may be highly active and desire tohave access to more information, such as insulin intake, activity,location of the Host, location of the Remote Monitors, and other data.Examples of other data can include: analyte measurements, ProcessedData, Contextual Data, Health Data, System Data, Treatment Data, UserData, Sensor Data, Summary Data, and/or any data described in thisdisclosure). The Host and/or Remote Monitor can toggle the viewing ofeach on/off for each Remote Monitor.

Another non-limiting example is Cell 1684, which allows a RemoteMonitor, Host, and/or other user to toggle on/off Remote Control. Insome implementations, a remote monitoring device can control a Host'streatment. Such control can include calibrating the host monitoringdevice or other devices (e.g., insulin administration using a medicamentdelivery pump). In some cases, for maintaining security, otherauthorizations (e.g., in addition or in the alternative to toggling on)can be used to allow the remote control of the remote monitoring device.For example, a Remote Monitor may need to authenticate himself orherself using a thumbprint, biometric sensor, password, passcode,authentication key, private/public passcode combination, etc. before theRemote Monitor can take remote control. As another non-limiting example,a Remote Monitor can be given control only in situations where he/she isin close proximity to the Host, where proximity (e.g., within 1000square meters or other determined ranges) can be determined based onlocators of the host monitoring device and remote monitoring device. Insome implementations, authentication can occur when another remotemonitoring device, the host monitoring device, and/or another device(e.g., any device described in this disclosure) verifies and/or approvesthe remote control. For example, a communication can go to anotherremote monitoring device and that Remote Monitor can approve the remotecontrol. In some cases, the approval communication may be sent in selectcases, such as if the Remote Monitor taking remote control wants to dosomething that is atypical or not something the programming of a hostmonitoring device and/or device would normally do (e.g., not following abolus calculator recommendation).

In some cases, it may also be desirable for a Host to take remotecontrol of a remote monitoring device. Such control can includecalibrating the remote monitoring device or other devices (e.g., insulinadministration using a medicament delivery pump). Similar authenticationand/or security can be built into such remote control as was describedfor remote control of a host monitoring device.

In some implementations, remote control can include approval. Forexample, a Host may desire to perform an action (e.g., administerinsulin and/or other mendicants). The Host can indicate (e.g., using amessage, selecting from a pulldown menu, hitting a button, etc.) thathe/she is going to perform such action, and/or such can be automaticallydetected by the host monitoring device based on various received data asdescribed herein. A host monitoring device can send a communication tothe remote monitoring device requesting approval for an intended action.For example, a child may want to administer insulin. The host monitoringdevice can detect that the child's insulin levels are low and that childis trying to administer insulin. The host monitoring device can send amessage and/or notification to the remote monitoring device indicatingthat the child would like to administer insulin. The child's parentusing the remote monitoring device, who may also be classified asPrimary Caretaker, can then approve or disapprove the administrationusing the remote monitoring device. For example, the message and/ornotification can come with options (e.g., buttons, pulldown menu, checkboxes, etc.), including “Approve” or “Disapprove,” that the parent canselect on a user interface.

In some cases, a Remote Monitor, Host, and/or other user can customizesettings for a classification, which can then be selected. For example,the alerts settings for a classification can be set, and then thatclassification with those settings can be assigned to a Remote Monitorusing Pull-down Menu 1602. In some implementations, differentclassifications and/or Remote Monitors can be notified differently basedon the urgency of a Host's condition.

In some implementations, setting the frequency of communications,rights, and/or privileges of Remote Monitors can be restricted, in whichonly some users have an ability to adjust those settings. For example, aHost (e.g., adult host) and/or an Administrator (e.g., adult caretakerof a child host, a parent/guardian or health care provider) can beprovided complete control over the communications, rights, and/orprivileges to be shared with his/her Remote Monitor(s). Advantageously,an Administrator can control in some cases when the Host is notcompetent to adequately manage the system (e.g., when Host is too young,too old, too busy, lacks the awareness and/or ability, has mentalchallenges, is injured, is diseased, etc.). Whether a Host and/orAdministrator controls, such controls can be set on a user interface ofa display of the host monitoring device (e.g., such as the example shownin FIG. 12). As a result, other users (e.g., users who are not the Hostand/or an Administrator) may not be able to control at least someaspects and/or functionalities of communications, rights, and/orprivileges for themselves and/or other users. In some implementations,various controls can be placed on customizable settings. For example,for the aforementioned other users (e.g., users who are not the Hostand/or Administrator), settings may not be configurable, may be limitedin valid values, and/or may have only selectable options from apredetermined list of options. In some cases, a Host and/orAdministrator can override any customizations made by a Remote Monitorand/or otherwise.

FIG. 16D illustrates an example display where customizations may berestricted by a Host, Administrator, and/or any other user with controlto restrict. Display 1686 can be displayed on a remote monitoring devicethat can be substantially similar to Remote Monitoring Device 300 and/orany other device described in this disclosure. Display 1686 can also bedisplayed on a host monitoring device and/or any other device describedin this disclosure. Contents of Display 1686 can be stored on a server(e.g., Secure Server 504). For example, when Display 1686 is displayedon a remote monitoring device and/or viewed by a Remote Monitor, Cell1688 can illustrate an example where settings cannot be changed by theRemote Monitor. The Remote Monitor using Display 1686 cannot modifyoptions in Cell 1688 (e.g., Remote Monitor cannot toggle on/off UrgentLow Alerts and/or set the glucose thresholds). Cell 1690 illustratesrestricted options of a Remote Monitor from a selection of predeterminedoptions. For example, Pulldown Menu 1692 can display predeterminedoptions from which the Remote Monitor can select values to populate thefield. Cell 1694 shows an example where the Remote Monitor can have someability to customize, but such ability is restricted. For example, theRemote Monitor can enter a value into Threshold 1696. However, the valueentered as Threshold 1696 has an upper limitation, where the RemoteMonitor cannot enter a value above the upper limitation. For example,Restriction 1698 indicates that the maximum is 65 minutes.

FIGS. 17A-D illustrate example customizable features of a Remote Monitorclassification definition. FIG. 17A illustrates communications settingsthat can be set for an example Remote Monitor classification/class. Suchsettings can be predefined or customized by a Remote Monitor, Host,and/or other user. Settings 1700 can allow communications to be set foran example Primary Remote Monitor class. Any other classificationdescribed in this disclosure can similarly be configured. For example,alert settings can be set using Cells 1704, 1712, 1722, 1734 which canbe substantially similar to Cells 1604, 1612, 1622, 1634, respectively.Cells 1752, 1754, 1756, 1782, 1784 can be substantially similar to Cells1652, 1654, 1656, 1682, 1684 as well. These settings, ones made, canaffect all Remote Monitors of a classification. In some cases,individual remote monitoring devices can have little or no ability tomodify their own settings (and/or the settings of any other remotemonitoring device and/or other devices described in this disclosure). Insuch cases, the settings for each individual remote monitoring devicecan be established by class definition settings and/or by individualsettings made by the Host and/or Administrator. In some implementations,remote monitoring devices may have at least some freedom to adjust oneor more settings in their communications, rights, and/or privileges,and/or the communications, rights, and/or privileges of other remotemonitoring devices and/or other devices described in this disclosure.

In some implementations, the predefined settings of remote monitors canbe initially set based on how active Remote Monitors are in predefinedclasses. For example, Primary Caretakers (in their respectiveclassifications) generally, can get more alerts and/or information thanother Remote Monitors. Moderately active Remote Monitors, such asTertiary Caretakers, may desire fewer alerts and/or information. Lowactive Remote Monitors, such as Social Associates, may desire even feweralerts and/or information.

As previously described, a Host and/or Administrator can restrict theability of some users (e.g., Remote Monitors and/or other users desiredto be restricted) to customize settings. By way of illustrative example,a Host using a host monitoring device can restrict one or more settings.For example, referring to FIG. 17A there can be restrict buttons, suchas Restrict Button 1736, that the Host can select when viewing Settings1700. Restrict Button 1736 can present a Host with various options torestrict how a Remote Monitor can configure a setting in his/her remotemonitoring device. FIG. 17D illustrates an example interface that couldpop up to allow the Host to configure how a Remote Monitor can berestricted. The interface can be displayed on a host monitoring device.In some implementations, the interface can be stored in memory on aserver (e.g., Secure Server 504) and/or displayed on a displaycommunicatively and/or operatively coupled to the server. Cell 1786 candisplay the cell that is to be configured for the Remote Monitor (e.g.,to view on the Remote Monitor's remote monitoring device), which in thisillustration is the Urgent Low Alert cell. Cell 1788 can present theoption of toggling on/off a Remote Monitor's ability to toggle on/offthe Urgent Low Alerts on his/her remote monitoring device. Cell 1790 canallow the Host to toggle on/off limits to threshold that a RemoteMonitor can enter into his/her Urgent Low Alert cell as viewed onhis/her remote monitoring device, in which the threshold can indicatethe glucose measurement below which an Urgent Low Alert is sent to theRemote Monitor's remote monitoring device. Cell 1792 can allow the Hostto disable a Remote Monitor's ability to enter a threshold at all,and/or lock the threshold value to the Host's determined value. Cell1794 can allow the Host to set a maximum value for the threshold thatthe Remote Monitor can enter. Cell 1796 can allow the Host to set aminimum value for the threshold that the Remote Monitor can enter. Insome cases, the Host can set a range of values for the threshold (e.g.,upper thresholds or lower thresholds) where a Remote Monitor can adjustthe threshold within the range to trigger communications. In someimplementations, thresholds can be set for other characteristics, suchas any category of data described herein. Cell 1798 can allow a Host todefine options for a Remote Monitor to choose from when setting thethreshold for Urgent Low Alerts (e.g., via a pulldown menu and/or byprompting Remote Monitor).

FIG. 18A illustrates an example where a Host communicates with aUniversal Remote Monitor in close proximity for assistance. In someimplementations, upon determining an inability of Remote Monitors toreact to an alert informative of a dangerous event associated with theanalyte state of Host, a server, handling the remote monitor operations,can assign a Universal Remote Monitor in close proximity to Host forobtaining assistance. For example, Host 1802 can have a host monitoringdevice that is followed by remote monitoring devices as describedherein. A first remote monitoring device can be associated with RemoteMonitor 1806, and a second remote monitoring device can be associatedwith Remote Monitor 1804. At a time when Host 1802 desires assistance,Remote Monitor 1806 may be unavailable or unable to assist. In somecases, Remote Monitor 1806 may not receive communications from Host1802's host monitoring device. In some cases, Remote Monitor 1806 cansend a response indicating it is unavailable. Remote Monitor 1804 may beavailable and can send and/or receive communications via Channel 1808.However, Remote Monitor 1804 may be too far away to provide timelyassistance. In such a case, Host 1802's host monitoring device cansearch for a Universal Remote Monitor within Area 1810, which can be apredefined area (e.g., 1000 square feet) and/or a predefined distance,typically (and/or contextually) defined with a proximity close enough totimely help Host 1802. For example, for a severe hyperglycemic response,the proximity may be within a few feet. As another non-limiting example,for a low, but not critically low, glucose reading, the proximity may bewithin a five minute travel distance (e.g., by car, bike, walking,running, etc.). In some cases, proximity can be as close as the closestUniversal Remote Monitor. In Area 1810, Universal Remote Monitor 1812can be in a position to assist. In some cases, notifying UniversalRemote Monitor 1812 can be reserved for high priority emergencies.

In some embodiments, a server handling remote monitoring operations(e.g., Secure Server 504), can receive location information of theHost-designated remote monitoring devices and Host's device. The servercan determine the ability or inability of each of Host-designatedselected remote monitoring devices to react to an alert informative of adangerous event associated with the analyte state of the Host based on aproximity of a Host-designated remote monitoring device to the Host'sdevice within a predetermined distance. The predetermined distance canbe set or derived as described above. Upon determining an inability ofall of Host-designated remote monitoring devices to react to an alert,the server can assign a universal remote monitoring device not amongHost-designated remote monitoring devices. The server, as part of theassigning process can generate a set of notifications rules pertainingto circumstances to send a message to the universal remote monitoringdevice informative of the dangerous event associated with the analytestate of the Host.

By way of illustrative example, Host 1802 can be attending a new schoolacross the country from his/her Remote Monitors (e.g., Remote Monitors1804, 1806). Host 1802's glucose level could drop to a low value, asmeasured by a host monitoring device. Universal Remote Monitor 1812could be another student who also attends the school and is in closeproximity within Area 1810. In this situation, Universal Remote Monitor1812 could receive a communication (e.g., an alert) to help. In somecases, Universal Remote Monitor 1812, and/or any other Universal RemoteMonitor, may need to pass a pre-approval process to become a UniversalRemote Monitor. Such pre-approval process can include a backgroundcheck, attending classes, and/or obtaining certain knowledge abouthelping diabetics and/or persons with health conditions. In some cases,a Universal Remote Monitor 1812 can become a Universal Remote Monitorbased on characteristics and/or expertise of Host 1802 and/or UniversalRemote Monitor 1812. For example, Universal Remote Monitor 1812 could bea medical professional with expertise in assisting diabetics. As anothernon-limiting example, Host 1802 could prefer a Universal Remote Monitorof the same gender as Host 1802. In some implementations, communicationsto Universal Remote Monitor 1812 can be anonymous and/or limited. Forexample, Universal Remote Monitor 1812 may only be able to see a definedsubset of data about Host 1802. Such subset of data can be based on thekinds of data Universal Remote Monitor 1812 would use to help Host 1802.In some cases, Hosts can be identified (e.g., by name, remote monitoringdevice serial number, nickname, classification, etc.) or be anonymous toUniversal Remote Monitor 1812. As another non-limiting example, acommunication channel between Universal Remote Monitor 1812 and one ormore of Host 1802's Remote Monitors (e.g., Remote Monitor 1804) could beopened so that Universal Remote Monitor 1812 could communicate with oneor more of those Remote Monitors. Such communication can include thetransmission of data that can assist Universal Remote Monitor 1812 inhelping Host 1802.

In some embodiments, as part of assigning a Universal Remote Monitor,the server assigns authorization to the Universal Remote Monitor foraccessing Host's data. The scope of the authorization can be determinedbased on what data may be of use to the Universal Remote Monitor (and/orthe characteristics or relationship between the Universal Remote Monitorand Host). In some embodiments, the authorization may be for a temporarytime frame. In some embodiments, Host 1802 may be prompted to accept ordecline the assignment of Universal Remote Monitor 1812. Host 1802 canalso determine the duration of the temporary time frame. In someimplementations, the server, handing the remote monitor operations(e.g., Secure Sever 510), can revoke the assignment of Universal RemoteMonitor 1812 if a Host-designated Remote Monitor is detected to beavailable and able to assist Host 1802. Revoking the assignment caninclude removing authorization of access previously granted to UniversalRemote Monitor 1812. The data made available to Universal Remote Monitor1812 can include one or more of (i) retrospective sensor data, (ii) realtime sensor data, (iii) a trend in the rate of change of the analytestate of Host 1802 or other data as described herein. In someimplementations, the analyte state includes the glucose level.

Proximity can have other implications. Remote Monitors may not only wantto know (e.g., be alerted) when a Host has an alert-worthy situation,but also may desire to know where the Host is presently located so thatthe Remote Monitor can take direct and/or indirect action to assist theHost. For example, a host monitoring device can send location data ofthe Host: (1) when a communication is generated (e.g., the recordedlocation data of the host associated with the CGM data that triggered analert), and/or (2) after the communication is triggered (e.g., in casethe Host is on the move, or has changed locations since an alert). Thelocation data can be received by a remote monitoring device, server,and/or any other device described in this disclosure. In some cases, aRemote Monitor's classification (e.g., hierarchical or lateral) candynamically change based on proximity. Such changes can be usercustomized (e.g., designated) or automatically changed based onpredefined class definitions. The changes can be stored in memory and/orprocessed by a remote monitoring device, host monitoring device, server,and/or any other device described in this disclosure.

In some cases, proximity can cause a host monitoring device totemporarily disable or enable alerts. FIG. 18B illustrates an examplewhere communications can be suppressed based on proximity. By way ofillustrative example, when Remote Monitor is able to receivecommunications from a Host's host monitoring device and/or otherdevices, one issue that can occur is duplicative communication. WhenRemote Monitor is nearby a Host (e.g., in the same room), communicationsmay be triggered between Host and Remote Monitor in such a way that thesame underlying communication can generate one or more simultaneousalarms, notifications or warnings between two or more devices. Suchduplicity can cause frustration, irritation, and/or annoyance.

In some implementation, a remote monitoring device (e.g., RemoteMonitoring Device 300), host monitoring device (e.g., Host MonitoringDevice 200), server (e.g., Secure Server 504), and/or any other devicedescribed in this disclosure can detect duplicative communications anddelay and/or suppress communications sent to one or more devices. Insome cases, such detection can be based on location, pattern ofcommunications, and/or responses by Remote Monitors and/or Hosts (e.g.,repeated ignoring of communications, any feedback indicative ofover/under communication, and/or user inputted changes to communicationsettings). In some cases, only certain kinds of communications may besuppressed. For example, a remote monitoring device, host monitoringdevice, server, and/or any other device described in this disclosure maysuppress all alerts except urgent alerts.

For example, Host 1860 can be in Area 1870 with Remote Monitors 1856,1858 and may desire to suppress and/or delay communications. As aresult, remote monitoring devices of Remote Monitors 1856, 1858 and/orthe host monitoring device of Host 1860 can suppress CommunicationChannels 1866, 1864. Such suppression can prevent communications frombeing sent and/or can turn off one or more sounds, vibrations, flashes,and/or other indicators of communication. In some implementations, thissuppression can be ordered from the host monitoring device. For example,the host monitoring device of Host 1860 can detect that the remotemonitoring devices of Remote Monitors 1856, 1558 are within Area 1870and not send communications to those remote monitoring devices. In someimplementations, suppression can occur by remote monitoring devices. Forexample, remote monitoring devices of Remote Monitor 1856 and/or 1858may detect whether they are within Area 1870, and decline to receivecommunications from the host monitoring device of Host 1860 when in Area1870. As another example, remote monitoring devices of Remote Monitors1856 and/or 1858 can receive communications from a host monitoringdevice of Host 1860 when within Area 1870, but not display suchcommunications. In some implementations, suppression can be handled by aserver. The server can receive the locations of each host monitoringdevice and/or remote monitoring device and not relay messages from hostmonitoring devices to remote monitoring devices when such remotemonitoring devices are within Area 1870 of the host monitoring device.

In some embodiments, the server handling the remote monitoringoperations (e.g., Secure Server 504), can process an alert informativeof a dangerous event associated with the analyte state of Host 1860. Theprocessed alert can be within a set of notification rules associatedwith at least one of the authorized remote monitoring devices (e.g.,remote monitoring devices 1854, 1856 and 1858). The server can receivean instruction to suppress sending the message associated with the alertone or more of the authorized remote monitoring devices. The server thencan suppress the sending of the message one or more of the authorizedremote monitoring devices.

In some embodiments, the dangerous event includes the analyte state ofHost 1860 exceeding a predetermined analyte concentration threshold or apredetermined rate of concentration change threshold. In someimplementations, processing the alert includes receiving alert data fromthe host monitoring device of Host 1869. The alert data can be generatedat one or both of the host monitoring device of Host 1860 or a sensorelectronics device in communication with the continuous analyte sensorof Host 1860. In some implementations, the server can generate the alertby processing the data to determine if the analyte state exceeds apredetermined analyte concentration threshold or a predetermined rate ofconcentration change threshold. In some implementations a secondpredetermined analyte concentration threshold lower than thepredetermined analyte concentration threshold can be defined. A secondpredetermined rate of concentration change threshold lower than thepredetermined rate of concentration change threshold can also bedefined. In the implementations defining these second thresholds, priorto suppressing a message, the analyte data can be processed to determinewhether the analyte state exceeds these second thresholds. If theanalyte state has exceeded the second thresholds, the instruction tosuppress is overridden and the message is sent to at least one of theauthorized remote monitoring devices after a predetermined delay.

Communications can be delayed, where the communications are not sentand/or displayed until after a determined amount of time (e.g., 0, 5,10, 15, 20, 30, 60 minutes or any number of minutes desirable includingany number of minutes between any of the aforementioned). In some cases,delays can be cued to events, such as where communications are delayedfrom being sent or displayed until a user wakes a device. As has beendescribed in this disclosure, delays can be handled by remote monitoringdevices, host monitoring devices, servers, and/or any other device inthis disclosure. In some implementations, when the communications aredelayed, the server can override an instruction to suppress thecommunication. In some cases, there can be other Remote Monitors, suchas Remote Monitor 1854, who are not in Area 1870 and who havecommunication channels such as Communication Channel 1862. Such RemoteMonitors may continue to have communications unimpeded.

Detection of whether Remote Monitors and Hosts are within a definedproximity can be accomplished using locators (e.g., Locators 206, 306)in remote monitoring devices, host monitoring devices, and/or any devicein this disclosure. For example, GPS can be used. As anothernon-limiting example, when a remote monitoring device receives an alert,it can start a Bluetooth or iBeacons scan for Host 1860's hostmonitoring device or other devices. If the remote monitoring devicedetects the host monitoring device and/or other devices (e.g., within 30feet for a Bluetooth detection), the remote monitoring device canexamine the Received Signal Strength Indicator (“RSSI”) to determine howclose (e.g., far, near, very near) it is to the host monitoring deviceand/or other device. When the remote monitoring device determines it isnear or very near the Host, the remote monitoring device can delayreceived communications (e.g., alerts) for a determined amount of time(e.g., one or two minutes) to give the Host a chance to respond. If theHost does respond within the determined amount of time, then the alertwould not sound on the remote monitoring device.

In some cases, it may be desirable for a Remote Monitor to receive morecommunications when in close proximity because the Remote Monitor can beof more help when in close proximity. In such cases, the aforementionedproximity detection can be used to increase alerts. In some cases,proximity can be used in conjunction with pattern recognition, such asany pattern recognition described in this disclosure, to determinewhether more or fewer communications are desirable.

FIG. 19 illustrates an example situation where a Host can preempt acommunication before it is sent to a Remote Monitor. For example, a Hostmay preempt a communication when the Host knows an event will happenand/or is addressing the event. Communications, such as alarms,typically lack the context for why they are triggered. Many, if notmost, alarms are not caused in emergency situations because the contextof the alarm (e.g., the situational factors of the Host) is typicallyunder the Host's control. For example, a Host may have missed a mealand/or eaten later than scheduled, undergone previously unplannedphysical activity, and/or been under unusual, excessive stress. Host maybe aware of and/or is capable of remedying these issues. For example, aHost can ingest or take a prescribed medicine (e.g., bolus insulin),modify behavior, eat extra snacks and/or meals to make-up for missed orlate meal, take additional rest to account for extra physical activity,engage in relaxation (e.g., by doing yoga, meditation, watching TV,etc.) to compensate for excessive stress. Yet, Host's Remote Monitor(s)may not be aware of Host's awareness and/or his/her actions to attend tothe situation. Therefore, increasing the amount of informational contextassociated with the alert would be beneficial to both Remote Monitor(s)and Host. Remote Monitors will be provided with peace of mind, knowingthat Host is responding appropriately to remedy the situation. Inaddition, Host will be relieved of the responsibility or obligation toexplain to Remote Monitor(s) why the alert was triggered.

In some cases, if a Host and/or Remote Monitor sees that the Host'sglucose level is dropping and/or trending downwards, he/she might wantto send out alerts, notifications, and/or other communications as soonas possible rather than wait until the glucose level falls below a lowerthreshold (e.g., Lower Threshold 1918). Or, Host might want to sendthese alerts or notifications before the glucose level rises above anupper threshold (e.g., Upper Threshold 1916). In some cases, Host cannotify Remote Monitors preemptively that a situation has been taken careof and/or give other contextual information that can help Remote Monitorunderstand future alerts, alarms, and/or communications sent by the hostmonitoring device. In some cases, such communications can include userpopulated and/or prepopulated messages. Based on predicted values,historical communication patterns, and/or other data described in thisdisclosure, a host monitoring device can send prepopulatedcommunications to Remote Monitors' remote monitoring devices indicatingthat a Host will be fine. In some implementations, a server (e.g.,Secure Server 504) can send the communications. The server can detectpatterns in Host data (e.g., whether Host is exercising, under stress,etc.) and send prepopulated messages to remote monitoring devices.

As another non-limiting example, a Host and/or Remote Monitor may wantto send a communication early. For example, if there are some futurerisks that a Host and/or Remote Monitor wants to make known to otherRemote Monitors, there can be a button that a Host and/or Remote Monitorcan press. In some implementations, a Host and/or Remote Monitor canotherwise use a user interface to send communications to one or moreRemote Monitors. In some cases, such communications can be prepopulatedbased on pattern recognition. For example, a host monitoring device can,at Point 1908, recognize that a Host's glucose level will fall belowLower Threshold 1918. Based on predicted values, historicalcommunication patterns, and/or other data described in this disclosure,a host monitoring device can send prepopulated communications to RemoteMonitors' remote monitoring devices indicating that Host may needassistance.

In some cases, it can also be desirable for a Host to temporarilydisable communications, increase delays, change thresholds, etc. TheHost may do so, for example, to avoid causing concern to Remote Monitorswhen the situation is already going to be taken care of by the Hostand/or a Caretaker. The Host can also temporarily disable communicationsfor other reasons, such as not wanting to show others an expected jumpin glucose for privacy reasons. As another example, certain events cancause expected jumps in glucose values (e.g., health or stress events).By being able to temporarily disable and/or limit communications, a Hostmay avoid judgment from his/her Remote Monitors for predictable and/orembarrassing high blood sugar levels. Temporarily disablingcommunications can be performed by a host monitoring device, remotemonitoring device, server, and/or any other device described in thisdisclosure. For example, a host monitoring device can temporarilydisable communications by temporarily not sending communications. Asanother non-limiting example, a remote monitoring device can temporarilydisable communications by temporarily not receiving communicationsand/or displaying communications. As another non-limiting example, aserver can temporarily disable communications by temporarily notrelaying communications (e.g., between host monitoring devices and/orremote monitoring devices) and/or by temporarily not displayingcommunications on displays coupled to the server.

As an illustrative example, Display 1900 can be displayed on a hostmonitoring device. Display 1900 can include Graph 1902, which caninclude analyte measurements such as glucose levels (e.g., EGV). Display1900 can also include Upper Threshold 1916 and Lower Threshold 1918. AtPoint 1908, a Host can notice that his/her glucose levels are trendingdownwards and may believe that measurements will fall below LowerThreshold 1918. This can cause an alarm, notification, and/or othercommunications to be sent to one or more remote monitoring devices. Notdesiring for such alarms, notifications, and/or other communications tobe sent, the Host can suppress those messages by selecting an option inthe display, such as Suppress Button 1922. In some implementations,pulling up a different display/page can allow suppression (e.g.,selecting Point 1908 and/or opening up a log can present an option forsuppression). When Suppress Button 1922 is selected, measurementsfalling below Lower Threshold 1918 may not cause an alarm, notification,and/or other communications to be sent from the host monitoring deviceto remote monitoring devices. In some implementations, suchcommunications can be modified and/or delayed.

In some cases, for safety reasons and/or otherwise, when a Hostsuppresses a communication, a new threshold can be set, in which, if theHost exceeds the new threshold in the case of a new upper threshold, orgoes below the new threshold in the case of a new lower threshold, analert, notification, and/or other communication can be sent. Having suchnew threshold can protect a Host against unexpected and/or unanticipatedeffects that can be dangerous. For example, after glucose levelsurpassing Point 1908, if Host hits Suppress Button 1922 to preventalarms, notifications, and/or other communications to be sent to remotemonitoring devices, a new lower threshold can be set, such as New LowerThreshold 1920. If glucose values fall below New Lower Threshold 1920,alerts, notifications, and/or other communications can be sent to remotemonitoring devices. In some implementations, determining whether a newupper threshold and/or a new lower threshold should be set can include apredictive calculation as described in this disclosure. When a futurepoint is projected to be below Lower Threshold 1918, a new lowerthreshold (e.g., New Lower Threshold 1920) can be used. When a futurepoint is projected to be above Upper Threshold 1916, a new upperthreshold can be used.

In some cases, suppression may only last for a determined number ofmeasurements and/or a determined amount of time before the suppressionis turned off. For example, at Point 1908, a host monitoring device maybe configured to suppress only the next 10 (or whatever number desired)measurements before communications are sent as usual. As anothernon-limiting example, communications may only be suppressed for 5minutes (or other desired time) before being sent as usual. In someimplementations, suppression can be turned off using patternrecognition. For example, at Point 1908, a user may suppresscommunications. Using any method described in this disclosure, a hostmonitoring device may detect when the Host's glucose levels go down andthen rebound back up, and may turn off suppression on the rebound.

As another non-limiting example, a host monitoring device and/or remotemonitoring device can increase or shorten a delay of a communication tobe sent to a Remote Monitor depending upon Host and/or Remote Monitoraction (e.g., treatment). The host monitoring device and/or remotemonitoring device can manage the increase or shortening of a delay of acommunication based on the type of communication, specific data withinthe communication, and/or other parameters to provide time to receivefeedback from Host/Remote Monitor about Host/Remote Monitor action(e.g., treatment). In some cases, a host monitoring device and/or remotemonitoring device can increase delays if a Host and/or Remote Monitormanually logs that a treatment has been performed. Similarly, that delaycan be decreased if the Host and/or Remote Monitors fails to acknowledgea communication and/or condition, and/or fail to act upon them.

In some cases, instead of preemption disabling (e.g., suppressing)communications, other communications can be sent. For example, insteadof an alert, a notification can be sent saying the Host's glucosemeasurement and/or that it is being taken care of. As anothernon-limiting example, instead of an alert, an entry in a log of glucosemeasurements can be made. In some implementations, preemption can behandled from a remote monitoring device where Remote Monitors preemptcommunications from being sent to one or more Remote Monitors (includingthemselves).

In some implementations, suppression can be done automatically throughpattern recognition. A remote monitoring device (e.g., Remote MonitoringDevice 300), host monitoring device (e.g., Host Monitoring Device 200),server (e.g., Secure Server 504), and/or any other device described inthis disclosure can recognize patterns in Host and/or Remote Monitordata in order to identify correlations with suppressed communications.In this way, communications can be preempted automatically when apattern reoccurs. For example, suppose a Host typically has a lowglucose reading around 11:30 AM before lunch. However, typically, theHost eats lunch soon thereafter and the low glucose reading is not anissue. A remote monitoring device (e.g., Remote Monitoring Device 300),host monitoring device (e.g., Host Monitoring Device 200), server (e.g.,Secure Server 504), and/or any other device described in this disclosurecan suppress any alerts, notifications, and/or communications, or modifythose alerts, notifications and/or communications, based on that patternof behavior.

In some cases, Remote Monitors not only want to know (e.g., be alerted,notified, and/or communicated to) when a Host has an alert-worthysituation, but Host's may also want to know if the Remote Monitor isactively following the Host's condition. In some circumstances, knowingwhen and/or how often Remote Monitors view a Host's communications canallow Hosts, Remote Monitors, and/or other users to better gauge how toset permissions and/or communications settings for individual RemoteMonitors based on what communications were sent to a Remote Monitor'sremote monitoring device, and/or whether (and/or how) suchcommunications were acknowledged by the Remote Monitor. Furthermore,affirmation that a Remote Monitor is viewing communications and/or datacan encourage Hosts to use features and/or continue certain activitiesand/or treatments.

In some implementations, a remote monitoring device (e.g., RemoteMonitoring Device 300), host monitoring device (e.g., Host MonitoringDevice 200), server (e.g., Secure Server 504), and/or any other devicedescribed in this disclosure can track a Remote Monitor's responsebehavior to communications, and/or provide overall monitoring of Host'sshared data. In some implementations, a host monitoring device and/orremote monitoring device can display a log/report showing the trackedbehavior to the Hosts and/or Remote Monitors. Such a log/report can alsobe stored in memory on a server and/or displayed on a displaycommunicatively and/or operatively coupled to the server.

FIG. 20 illustrates an example Remote Monitor Response Log showing how aRemote Monitor responded to communications. Remote Monitor Response Log2000 can be stored in memory and/or displayed on a remote monitoringdevice (e.g., Remote Monitoring Device 300), host monitoring device(e.g., Host Monitoring Device 200), and/or any other device described inthis disclosure. In some cases, a server (e.g., Secure Server 504) canstore Log 2000 in memory and/or display Log 2000 on a displaycommunicatively and/or operatively coupled to the server. Remote MonitorResponse Log 2000 can include entries such as Entry 2002. These entriescan state a communication received by a Remote Monitor and/or thatRemote Monitor's response. For example, Entry 2002 can state that RemoteMonitor received an alert stating the Host had a glucose reading of 205mg/dL at school. Entry 2002 can also state what the Remote Monitor did,which as illustrated, shows the Remote Monitor sent a message inresponse. In some implementations, clicking on text such as “sentmessage” can allow a viewer to see the text of the message and/or otherrelated data and logs.

Remote Monitor Responses Log 2000 can allow a viewer to see what kindsof communications a Remote Monitor received and/or the Remote Monitor'sresponses to such messages. In some cases, this can allow the viewer tomanually examine the communications and/or responses, and/or actaccordingly. Such actions can include changing the settings and/orpermissions of the Remote Monitor (e.g., adjusting frequency ofcommunications, rights, and/or privileges of a Remote Monitor, such asby using settings as discussed with reference to FIGS. 16A-D and/orFIGS. 17A-D).

In some implementations, a remote monitoring device (e.g., RemoteMonitoring Device 300), host monitoring device (e.g., Host MonitoringDevice 200), server (e.g., Secure Server 504), and/or any other devicedescribed in this disclosure can perform pattern recognition and/oradjust settings (e.g., frequency of communications, rights, and/orprivileges of a Remote Monitor) and/or give automatic responses based onlearned behavior from historical Host/Remote Monitor actions. As anillustrative example, a remote monitoring device can examine a RemoteMonitor's communication-response behavior and determine that a RemoteMonitor always sends messages after receiving a low alert. The remotemonitoring device can then create prepopulated messages and/or makesuggested responses for the Remote Monitor when the Remote Monitorreceives a low alert. As another example, when a Remote Monitor alwaysignores low alerts, a host monitoring device can stop sending thatRemote Monitor's remote monitoring device low alerts. In some cases, aRemote Monitor's classification can change based on the Remote Monitor'sresponsiveness. As an illustrative example, a Primary Caretaker who isunresponsive may be moved down to a Secondary Caretaker. The recognitionof unresponsiveness and/or movement of the Primary Caretaker toSecondary Caretaker can be performed by host monitoring devices, remotemonitoring devices, servers, and/or other devices. In some cases, when aRemote Monitor is not responsive to certain communications, suchcommunications can be sent to another Remote Monitor.

In some cases, it may be desirable for a host monitoring device and/orremote monitoring device to include the ability to self-monitor itscomponents. Such can allow malfunctions and/or hardware/softwareproblems to be detected before they interfere with health monitoring.

In some implementations, such self-monitoring can be accomplished byusing components of host monitoring devices and/or remote monitoringdevices to monitor other components in that same device. For example, amicrophone can detect if the speaker is functioning, an accelerometercan detect if the vibrator motor is functioning, or an optical sensorcan detect optical data to monitor the display. Such self-monitoring canbe included in System Data. In some implementations, a test sequence canbe run to test one or more components of a host monitoring device and/orremote monitoring device. Such test sequence can be initiated by therespective host monitoring device and/or remote monitoring device,and/or other host monitoring devices and/or remote monitoring devices inthe monitoring network. In some cases, a server can initiate the testsequence on one or more of the host monitoring devices and/or remotemonitoring devices in the monitoring system.

In some implementations, a remote monitoring device can receiveself-monitored data about a host monitoring device. The remotemonitoring device can receive the self-monitored data to display to theRemote Monitor. This self-monitored data can give the Remote Monitorpeace of mind that the host monitoring device is properly functioning,which may be indicative of whether the Host is able to receive an alarm.If failures are found, diagnostics can identify where the problem mightbe and determine whether the failures are clinically risky. For example,if speakers of a host monitoring device are not working, it could beclinically risky because a Host may not receive communications such asalerts and alarms. In some cases, communications regarding a failing ormuted host monitoring device may be escalated because Host may not beable to see and/or hear clinically important alarms. Examples ofescalation can include: alerts to Remote Monitors escalating faster,fewer delays, changes in kind of alert, alerting different RemoteMonitors and alerting Remote Monitors of a different classification,alerting Universal Remote Monitors, etc.

In the case of remote monitoring device failure, for example, asindicated by self-monitoring data, the Remote Monitor's classificationcan be altered. For example, if the Remote Monitor with a failing remotemonitoring device was the Primary Caretaker, a different Remote Monitorcould become a Primary Caretaker, and the Remote Monitor with thefailing remote monitoring device could be reclassified.

In some cases, the remote monitoring device, such as a Remote Monitor'ssmartphone operating a remote monitoring software application (e.g.,“remote monitoring app”), may be set up and/or used by the RemoteMonitor with a low volume setting or a mute option such that therespective Remote Monitor may miss alarms and/or notifications about theHost's analyte state sent to the remote monitoring device. Such settingscan be detected and overridden to reliably deliver such alarms and/ornotifications to Remote Monitor.

In some implementations, remote monitoring app can include a method foroverriding a low volume setting, mute or other non-disturb mode set bythe Remote Monitor on his/her remote monitoring device. For users'mobile computing devices that include appropriate vibration hardware tocreate a vibrate action (such as smartphones) and do not disturb (DND)modes on their operating systems, the remote monitoring app can beconfigured to override the mute switch or DND modes set by the RemoteMonitor on their smartphone, such as phone calls, texts, notifications,or other alerts, to reliably alert the Remote Monitor of the Host'sanalyte condition in a manner that respects the Remote Monitor's desireto be uninterrupted, and therefore reduce alert fatigue. Illustratively,it is necessary that a Host reacts appropriately to certain states orcircumstances associated with the Host's medical condition. Using theremote monitoring systems and methods in accordance with the disclosedembodiments, a Remote Monitor can supplement or augment the Host'smanagement of his/her medical condition by checking on the Host,particularly when the Host's state is in alert. Therefore, it isimportant that the Remote Monitor also receive the alarms pertaining tothe Host's medical condition (e.g., analyte levels and trend) topromptly and properly react to their condition. However, Remote Monitorsmust balance their responsibility as a remote monitor of a Host with thenumerous interruptions of life, which often occur on the same remotemonitoring device as the remote monitoring app, i.e., the smartphone,tablet and/or smart wearable device. Thus, in some embodiments, theremote monitoring app provides an intelligent alert process to deliverthe Host's analyte-related alerts when Remote Monitor's remotemonitoring device is set to mute, low volume, and/or DND mode. Forexample, the intelligent alert process is implemented automatically bythe remote monitoring app, so that setup by the Remote Monitor is notrequired.

Examples

In some embodiments of the present technology (example 1), a method forremote monitoring of a subject's health data by authorized monitorsincludes receiving, at a secure server, data associated with an analytestate of a host that is provided by a host device operable to receivesensor data generated by a continuous analyte sensor worn by the host,in which one or more remote monitoring devices are authorized by thesecure server to access permissible data of the received data stored onthe secure server based on a set of permissions pre-selected andmodifiable by the host for each remote monitoring device, in which thepermissions are associated with what data is available to a remotemonitoring device once authorized; generating, at the server, aplurality of classifications including a first classification and asecond classification of the remote monitoring devices authorized toaccess permissible data, in which a classification of the remotemonitoring devices designates a hierarchy to provide communicationsbased on notifications rules to inform an authorized remote monitoringdevice about the host's analyte state; and assigning, at the server,each of the remote monitoring devices to one of the plurality ofclassifications, in which the second classification includes one or bothof (i) greater restrictions to the permissible data than that of thefirst classification, and (ii) more restrictive notification rules thanthe first classification.

Example 2 includes the method of example 1, in which assignment of theremote monitoring device to the first and second classifications isbased on one or more of locations of the host device and the remotemonitoring devices, a characteristic of a user of the remote monitoringdevice communicated to the server by the user's remote monitoringdevice, a relationship between the user of the remote monitoring deviceand the host, or a behavior of a remote monitoring device.

Example 3 includes the method of example 1, in which assignment of theremote monitoring device to the first and second classifications isbased at least in part on locations of the host device and the remotemonitoring devices.

Example 4 includes the method of examples 2 or 3, further includingreceiving, at the server, the locations of the host device and theremote monitoring devices; relegating, by the server, a remotemonitoring device from the first classification to the secondclassification when the remote monitoring device exceeds a predeterminedproximity from the host device.

Example 5 includes the method of example 1, in which assignment of theremote monitoring device to the first and second classifications isbased at least in part on one or more characteristics of the users ofthe remote monitoring devices.

Example 6 includes the method of examples 2 or 5, in which thecharacteristics include health data associated with the user of theremote monitoring device collected by one or more of a continuousglucose monitor, a heart rate monitor, or other health monitoringdevice.

Example 7 includes the method of examples 2 or 5, in which thecharacteristics include an activity status associated with the user ofthe remote monitoring device including an available status, a busystatus, or a sleep status.

Example 8 includes the method of example 1, in which assignment of theremote monitoring device to the first and second classifications isbased at least in part on a relationship of the remote monitor user andthe host.

Example 9 includes the method of examples 2 or 8, in which the firstclassification includes the remote monitor user being a primarycaretaker of the host, and the second classification includes the remotemonitor user being one or more of a primary caretaker, an assignedwatcher of the host, a friend of the host, or a family member of thehost.

Example 10 includes the method of example 1, in which assignment of theremote monitoring device to the first and second classifications isbased at least in part on a behavior of a remote monitoring device.

Example 11 includes the method of example 2 or 10, further includingproviding, by the server, a message informative of an event associatedwith the analyte state of the host to a first remote monitoring deviceassigned to the first classification; and relegating, by the server, thefirst remote monitoring device from the first classification to thesecond classification based at least in part on a lack of acknowledgmentby the first remote monitoring device within a predetermined time periodafter the providing the message.

Example 12 includes the method of example 11, in which the providingincludes providing a plurality of messages informative of a plurality ofrespective events to the first monitoring device over a duration oftime, and the relegating is based on the lack of acknowledgment of thefirst monitoring device to a predetermined number of instances of theplurality of the provided messages.

Example 13 includes the method of examples 2 or 10, further includingproviding, by the server, a message informative of an event associatedwith the analyte state of the host to a first remote monitoring deviceassigned to the second classification; and elevating, by the server, thefirst remote monitoring device from the second classification to thefirst classification based at least in part on acknowledgment by thefirst remote monitoring device within a predetermined time period afterthe providing the message.

Example 14 includes the method of example 13, in which the providingincludes providing a plurality of messages informative of a plurality ofrespective events to the first monitoring device over a duration oftime, and the elevating is based at least in part on the acknowledgmentof the first monitoring device to a predetermined number of instances ofthe plurality of the provided messages.

Example 15 includes the method of examples 1 or 2, in which theplurality of classifications includes a third classification of theremote monitoring devices authorized to access permissible data, inwhich the third classification includes one or both of (i) greaterrestrictions to the permissible data than that of the firstclassification or the second classification or both, and (ii) morerestrictive notification rules than the first classification or thesecond classification or both.

Example 16 includes the method of example 1, in which the authorizedremote monitoring devices include a first remote monitoring deviceoperated by a first remote monitor user and a second remote monitoringdevice operated by a second remote monitor user, in which the firstremote monitoring device is assigned to the first classification, andthe second remote monitoring device is assigned to the secondclassification.

Example 17 includes the method of example 16, in which the first andsecond remote monitoring devices are in wireless communication with eachother.

Example 18 includes the method of examples 16 or 17, further includingreceiving, at the server, a request from the first monitoring device toelevate the second remote monitoring device to the first classification;and elevating, by the server, the second remote monitoring device fromthe second classification to the first classification after acceptanceof the request.

Example 19 includes the method of example 18, further including prior tothe elevating, accepting, by the server, the request based on anestablished awareness by the second remote monitoring device to acceptprivileges and duties associated with the first classification.

Example 20 includes the method of example 16, further includingproviding, by the server, an alert informative of an event associatedwith the analyte state of the host to the first remote monitoring devicebased on the notification rules associated with the firstclassification; receiving, at the server, a response from the firstremote monitoring device indicative of inability to react to the alertor a lack of response from the first remote monitoring device within apredetermined time period after the providing the alert; and responsiveto the receiving the response from the first remote monitoring device,providing, by the server, the alert to the second remote monitoringdevice.

Example 21 includes the method of example 20, further includingreceiving, at the server, a response from the second remote monitoringdevice indicative of ability to react to the alert.

Example 22 includes the method of example 21, further includingelevating, by the server, the second remote monitoring device from thesecond classification to the first classification based at least in parton acknowledgment by the second remote monitoring device within thepredetermined time duration after the providing the alert.

Example 23 includes the method of example 20, further includingrelegating, by the server, the first remote monitoring device from thefirst classification to the second classification based on the responseindicative of inability or the lack of response.

Example 24 includes the method of example 20, in which the alertincludes information outside of the notification rules associated withthe second classification; and the method further includes, prior to theproviding the alert to the second remote monitoring device, overriding,by the server, the notification rules associated with the secondclassification for the alert to be provided to the second remotemonitoring device based on a severity factor of the informationassociated with the alert.

Example 25 includes the method of examples 1-24, in which the analytestate includes glucose level.

Example 26 includes the method of examples 1-25, in which thenotification rules define circumstances to send a message to arespective remote monitoring device informative of an event associatedwith the analyte state of the host, and in which the notification rulesare modifiable by the authorized remote monitoring devices within ascope of the set of permissions to the data associated with therespective remote monitoring device.

Example 27 includes the method of examples 1-25, in which thepermissible data includes (i) retrospective sensor data, (ii) real timesensor data, and (iii) a trend in the rate of change of the analytestate of the host.

In some embodiments of the present technology (example 28), a method forremote monitoring of a subject's health data by authorized monitorsincludes receiving, at a secure server, data associated with an analytestate of a host that is provided by a host device operable to receivesensor data generated by a continuous analyte sensor worn by the host,in which a plurality of remote monitoring devices are authorized by thesecure server to access permissible data of the received data stored onthe secure server based on a set of permissions pre-selected andmodifiable by the host for each remote monitoring device, in which thepermissions are associated with what data is available to a remotemonitoring device once authorized; providing, by the server, an alertinformative of an event associated with the analyte state of the host toselected remote monitoring devices based on notification rules thatdefine circumstances to send the alert to a respective remote monitoringdevice, in which the notification rules are modifiable by the authorizedremote monitoring devices within a scope of the set of permissions tothe data associated with the respective remote monitoring device;receiving, at the server, a response from one or more of the selectedremote monitoring device; and processing, by the server, the receivedresponse to determine the ability or inability of the selected remotemonitoring device corresponding to the received response to react to thealert.

Example 29 includes the method of example 28, in which the receivingincludes a plurality of responses corresponding from a plurality of theselected remote monitoring devices, in which the received responses areindicative of at least one of the selected remote monitoring deviceshaving the ability to react to the alert.

Example 30 includes the method of example 29, further includingproviding, by the server, a message to the selected remote monitorsindicating that the at least one of the selected remote monitoringdevices has indicated the ability to react to the alert.

Example 31 includes the method of example 30, in which the providing themessage includes providing a log of the received responses by theselected remote monitors.

Example 32 includes the method of examples 28, 29, 30 or 31, furtherincluding generating, at the server, a plurality of classificationsincluding a first classification and a second classification of theremote monitoring devices authorized to access permissible data, inwhich a classification of the remote monitoring devices designates ahierarchy to provide communications based on the notifications rules;and assigning, at the server, each of the remote monitoring devices toone of the plurality of classifications, in which the secondclassification includes one or both of (i) greater restrictions to thepermissible data than that of the first classification, and (ii) morerestrictive notification rules than the first classification.

Example 33 includes the method of examples 28-32, in which thepermissible data includes (i) retrospective sensor data, (ii) real timesensor data, and (iii) a trend in the rate of change of the analytestate of the host.

Example 34 includes the method of examples 28-33, in which the analytestate includes glucose level.

In some embodiments of the present technology (example 35), a method forremote monitoring of a subject's health data by authorized monitorsincludes receiving, at a secure server, data associated with an analytestate of a host that is provided by a host device operable to receivesensor data generated by a continuous analyte sensor worn by the host,in which a plurality of host-designated remote monitoring devices areauthorized by the secure server to access permissible data of thereceived data stored on the secure server based on a set of permissionspre-selected and modifiable by the host for each host-designated remotemonitoring device, in which the permissions are associated with whatdata is available to a remote monitoring device once authorized;receiving, by the server, location information of the host-designatedremote monitoring devices and the host device; determining, by theserver, the ability or inability of each of the host-designated selectedremote monitoring devices to react to an alert informative of adangerous event associated with the analyte state of the host based on aproximity of a host-designated selected remote monitoring device to thehost device within a predetermined distance; upon the determining theinability of all of the host-designated selected remote monitoringdevices to react to an alert, assigning, by the server, a universalremote monitoring device not among the host-designated selected remotemonitoring devices, in which the assigning includes generating a set ofnotifications rules pertaining to circumstances to send a message to theuniversal remote monitoring device informative of the dangerous eventassociated with the analyte state of the host.

Example 36 includes the method of example 35, in which the assigning theuniversal remote monitoring device to at least some of the dataassociated with the analyte state of the host includes authorization toaccess the at least some of the data for a temporary time frame.

Example 37 includes the method of examples 35 or 36, further includingproviding, by the server, a communication to the host device informativeof assignment of the universal remote monitoring device and promptingthe host device to accept or decline the assignment.

Example 38 includes the method of example 37, receiving, at the server,a response communication by the host device with an acceptance ordeclination of the assignment.

Example 39 includes the method of example 38, in which the temporarytime frame is determined by the host device.

Example 40 includes the method of example 35, further including upon thedetermining the ability of at least one of the host-designated selectedremote monitoring devices to react to an alert, revoking, by the server,assignment of the universal remote monitoring device, in which therevoking includes removing access of the universal remote monitoringdevice to at least some of the data associated with the analyte state ofthe host.

Example 41 includes the method of examples 35-40, in which thenotification rules are within a scope of the set of permissions to thedata associated with the host-designated remote monitoring devices.

Example 42 includes the method of examples 35-40, in which the dataincludes one or more of (i) retrospective sensor data, (ii) real timesensor data, or (iii) a trend in the rate of change of the analyte stateof the host.

Example 43 includes the method of example 35-42, in which the analytestate includes glucose level.

In some embodiments of the present technology (example 44), a method forremote monitoring of a subject's health data by authorized monitorsincludes receiving, at a secure server, data associated with an analytestate of a host that is provided by a host device operable to receivesensor data generated by a continuous analyte sensor worn by the host,in which one or more remote monitoring devices are authorized by thesecure server to access permissible data of the received data stored onthe secure server based on a set of permissions pre-selected andmodifiable by the host for each remote monitoring device, in which thepermissions are associated with what data is available to a remotemonitoring device once authorized, and in which the one or more remotemonitoring devices are assigned notification rules that definecircumstances to send a message to a respective remote monitoring deviceinformative of an event associated with the analyte state of the host,in which the notification rules are modifiable by the authorized remotemonitoring devices within a scope of the set of permissions to the dataassociated with the respective remote monitoring device; processing, bythe server, an alert informative of a dangerous event associated withthe analyte state of the host, in which the processed alert is within aset of notification rules associated with at least one of the authorizedremote monitoring devices; receiving, by the server, an instruction tosuppress sending the message associated with the alert to the at leastone of the authorized remote monitoring devices; and suppressing, by theserver, the sending of the message to the at least one of the authorizedremote monitoring devices.

Example 45 includes the method of example 44, in which the dangerousevent includes the analyte state of the host exceeding a predeterminedanalyte concentration threshold or a predetermined rate of concentrationchange threshold.

Example 46 includes the method of example 44, in which the processingthe alert includes receiving alert data from the host device, in whichthe alert data is generated at one or both of the host device or asensor electronics device in communication with the continuous analytesensor.

Example 47 includes the method of example 44, in which the processingthe alert includes generating, by the server, the alert by processingthe data to determine if the analyte state exceeds the predeterminedanalyte concentration threshold or the predetermined rate ofconcentration change threshold.

Example 48 includes the method of example 44, further including sendingthe message associated with the alert to the at least one of theauthorized remote monitoring devices after a predetermined delay.

Example 49 includes the method of example 48, in which the sending themessage includes overriding, by the server, the received instruction tosuppress.

Example 50 includes the method of example 44, further including prior tothe suppressing, processing the data to determine if the analyte stateexceeds a second predetermined analyte concentration threshold lowerthan the predetermined analyte concentration threshold or a secondpredetermined rate of concentration change threshold lower than thepredetermined rate of concentration change threshold, in which, if theanalyte state exceeds the second predetermined analyte concentrationthreshold or the second predetermined rate of concentration changethreshold, sending the message associated with the alert to the at leastone of the authorized remote monitoring devices after a predetermineddelay, in which the sending includes overriding the received instructionto suppress.

Example 51 includes the method of examples 44-50, in which thepermissible data includes (i) retrospective sensor data, (ii) real timesensor data, and (iii) a trend in the rate of change of the analytestate of the host.

Example 52 includes the method of examples 44-51, in which the analytestate includes glucose level.

In some embodiments of the present technology (example 53), a method forremote monitoring of a subject's health data by authorized monitorsincludes receiving, at a secure server, data associated with an analytestate of a host that is provided by a host device operable to receivesensor data generated by a continuous analyte sensor worn by the host,in which one or more remote monitoring devices are authorized by thesecure server to access permissible data of the received data stored onthe secure server based on a set of permissions pre-selected andmodifiable by the host for each remote monitoring device, in which thepermissions are associated with what data is available to a remotemonitoring device once authorized; providing, by the server, anotification informative of an event associated with the analyte stateof the host to selected remote monitoring devices based on notificationrules that define circumstances to send the notification to a respectiveremote monitoring device, in which the notification rules are modifiableby the authorized remote monitoring devices within a scope of the set ofpermissions to the data associated with the respective remote monitoringdevice; and providing, by the server, contextual information with thenotification, the contextual information including a time, an amount,and/or a type of (i) a medicament taken by the host, (ii) a food ordrink ingested by the host, (iii) an exercise or activity undertaken bythe host, (iv) a level of stress experienced by the host, or (v) anenvironmental condition experienced by the host, or a combination of(i)-(vi) thereof.

Example 54 includes the method of example 53, in which the exercise oractivity undertaken by the host includes one or more of running,walking, swimming, skiing or snowboarding, skateboarding, biking, weightlifting, sitting, resting, or sleeping.

Example 55 includes the method of example 53, in which the level ofstress experienced by the host includes one or more of acute or episodicacute stress, chronic stress, high stress, medium stress, low stress, nostress, anxiety, emotional stress, or panic attack.

Example 56 includes the method of example 53, in which the environmentalcondition experienced by the host includes one or more of weather,humidity, pressure, temperature, scenery, location, or situationincluding at work, at school, or on break or vacation.

Example 57 includes the method of example 53, in which the notificationincludes an alert informative of a dangerous event associated with theanalyte state of the host.

Example 58 includes the method of example 53, further includinggenerating, at the server, a plurality of classifications including afirst classification and a second classification of the remotemonitoring devices authorized to access permissible data, in which aclassification of the remote monitoring devices designates a hierarchyto provide communications based on the notifications rules; andassigning, at the server, each of the remote monitoring devices to oneof the plurality of classifications, in which the second classificationincludes one or both of (i) greater restrictions to the permissible datathan that of the first classification, and (ii) more restrictivenotification rules than the first classification.

Example 59 includes the method of example 58, further including prior tothe providing contextual information with the notification, determining,by the server, an assigned classification of the respective remotemonitoring device to receive the notification; and if the respectiveremote monitoring device is assigned to the first classification, thenproviding the contextual information with the notification, and if therespective remote monitoring device is assigned to the secondclassification, then not providing the contextual information with thenotification or providing a limited amount of the contextual informationwith the notification.

Example 60 includes the method of example 59, in which the limitedamount of the contextual information is based on a predeterminedcategorization determined by the host device.

Example 61 includes the method of example 53, further includingreceiving, at the server, a response from at least one of the remotemonitoring devices, in which the received response includes contextualdata of a remote monitor user operating the respective remote monitoringdevice, the contextual data including a time, an amount, and/or a typeof (i) an activity undertaken by the remote monitor user, (ii) a levelof stress experienced by the remote monitor user, or (iii) anenvironmental condition experienced by the remote monitor user, or acombination of (i)-(iii) thereof.

Example 62 includes the method of example 61, further includingprocessing, by the server, the received response to determine theability or inability of the at least one remote monitoring device toreact to an alert based on the contextual data.

Example 63 includes the method of example 62, in which, when thecontextual data includes an activity, level of stress, or environmentalcondition of the remote monitor user indicative of the inability toreact to an alert, the method further includes providing, by the server,a communication to the host device including at least some of thecontextual data of the received response.

Example 64 includes the method of example 62, in which, when thecontextual data includes an activity, level of stress, or environmentalcondition of the remote monitor user indicative of the inability toreact to an alert, the method further includes providing, by the server,a communication to other remote monitoring devices indicating that theat least one remote monitoring device is unable to react to alerts.

Example 65 includes the method of examples 53-64, in which thepermissible data includes (i) retrospective sensor data, (ii) real timesensor data, and (iii) a trend in the rate of change of the analytestate of the host.

Example 66 includes the method of examples 53-65, in which the analytestate includes glucose level.

Example 67 includes a continuous analyte sensor system including acontinuous analyte sensor device worn by the host including thecontinuous analyte sensor to detect signals associated with an analyteof the host, and a sensor electronics module to perform at least someprocessing of the signals to generate sensor data and transmitting thesensor data to the host device; a non-transitory computer programproduct at least partially stored on the host device and includinginstructions that, when executed by a processor of the host device,causes the processor to perform at least some processing of the sensordata to produce the data associated with the analyte state of the host;and the secure server in communication with the host device to performthe method of any of the aforementioned examples 1-66.

In some implementations, a computing system that has componentsincluding a central processing unit (“CPU”), input/output (“I/O”)components, storage, and memory can be used to execute the monitoringsystem, or specific components and/or subcomponents of the monitoringsystem. The executable code modules of the monitoring system can bestored in the memory of the computing system and/or on other types ofnon-transitory computer-readable storage media. In some implementations,monitoring system can be configured differently than described above.

Each of the processes, methods, and algorithms described in thepreceding sections can be embodied in, and fully or partially automatedby, code modules executed by one or more computers, computer processors,or machines configured to execute computer instructions. The codemodules can be stored on any type of non-transitory computer-readablemedium or tangible computer storage device, such as hard drives, solidstate memory, optical disc, and/or the like. The systems and modules canalso be transmitted as generated data signals (e.g., as part of acarrier wave or other analog or digital propagated signal) on a varietyof computer-readable transmission mediums, including wireless-based andwired/cable-based mediums, and can take a variety of forms (e.g., aspart of a single or multiplexed analog signal, or as multiple discretedigital packets or frames). The processes and algorithms can beimplemented partially or wholly in application-specific circuitry. Theresults of the disclosed processes and process steps can be stored,persistently or otherwise, in any type of non-transitory.

The various features and processes described above can be usedindependently of one another, or can be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks can be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described tasks or eventscan be performed in an order other than that specifically disclosed, ormultiple can be combined in a single block or state. The example tasksor events can be performed in serial, in parallel, or in some othermanner. Tasks or events can be added to or removed from the disclosedexample implementations. The example systems and components describedherein can be configured differently than described. For example,elements can be added to, removed from, or rearranged compared to thedisclosed example implementations.

Conditional language used herein, such as, among others, “can,” “could,”“might,” “may,” “e.g.,” and the like, is not generally intended to implythat features, elements and/or steps are required for one or moreimplementations or that one or more implementations necessarily includelogic for deciding, with or without author input or prompting, whetherthese features, elements and/or steps are included or are to beperformed in any particular embodiment. The terms “comprising,”“including,” “having,” and the like are synonymous and are usedinclusively, in an open-ended fashion, and do not exclude additionalelements, features, acts, operations, and so forth. Also, the term “or”is used in its inclusive sense (and not in its exclusive sense) so thatwhen used, for example, to connect a list of elements, the term “or”means one, some, or all of the elements in the list. Conjunctivelanguage such as the phrase “at least one of X, Y and Z,” unlessspecifically stated otherwise, is otherwise understood with the contextas used in general to convey that an item, term, etc. can be either X, Yor Z. Thus, such conjunctive language is not generally intended to implythat certain implementations require at least one of X, at least one ofY and at least one of Z to each be present. The terms “about” or“approximate” and the like are synonymous and are used to indicate thatthe value modified by the term has an understood range associated withit, where the range can be ±20%, ±15%, ±10%, ±5%, or ±1%. The term“substantially” is used to indicate that a result (e.g., measurementvalue) is close to a targeted value, where close can mean, for example,the result is within 80% of the value, within 90% of the value, within95% of the value, or within 99% of the value. Also, as used herein“defined” can include “predefined” and/or otherwise determined values,conditions, thresholds, measurements, and the like.

While certain example implementations have been described, theseimplementations have been presented by way of example only, and are notintended to limit the scope of the inventions disclosed herein. Thus,nothing in the foregoing description is intended to imply that anyparticular feature, characteristic, step, module, or block is necessaryor indispensable. Indeed, the methods and systems described herein canbe embodied in a variety of other forms; furthermore, various omissions,substitutions and changes in the form of the methods and systemsdescribed herein can be made without departing from the spirit of theinventions disclosed herein.

What is claimed is:
 1. A method for remote monitoring health data,comprising: receiving, at a secure server, data associated with ananalyte state of a host that is provided by a host device operable toreceive sensor data generated by a continuous analyte sensor worn by thehost, wherein a plurality of host-designated remote monitoring devicesare authorized by the secure server to access permissible data of thereceived data stored on the secure server based on a set of permissionspre-selected and modifiable by the host for each of the plurality ofhost-designated remote monitoring devices, wherein the permissions areassociated with what data is available to each of the plurality ofhost-designated remote monitoring devices once authorized; receiving, bythe secure server, location information of each of the plurality ofhost-designated remote monitoring devices and the host device;determining, by the secure server, an ability or inability of each ofthe plurality of host-designated remote monitoring devices to react toan alert informative of a dangerous event associated with the analytestate of the host, wherein the ability or the inability of a respectivehost-designated remote monitoring device to react is based on aproximity of the respective host-designated remote monitoring device tothe host device being within a predetermined distance, wherein thepredetermined distance is determined based at least in part on aseverity of the dangerous event, and wherein the severity of thedangerous event has an inverse relationship with a size or length of thepredetermined distance; and upon determining the inability of all of theplurality of host-designated remote monitoring devices to react to thealert, assigning, by the secure server, a universal remote monitoringdevice not among the plurality of host-designated remote monitoringdevices, wherein the assigning includes generating a set of notificationrules pertaining to circumstances to send a message to the universalremote monitoring device informative of the dangerous event associatedwith the analyte state of the host.
 2. The method of claim 1, whereinthe assigning the universal remote monitoring device to at least some ofthe data associated with the analyte state of the host includesauthorization to access the at least some of the data for a temporarytime frame.
 3. The method of claim 1, further comprising: providing, bythe secure server, a communication to the host device informative ofassignment of the universal remote monitoring device and prompting thehost device to accept or decline the assignment.
 4. The method of claim3, receiving, at the secure server, a response communication by the hostdevice with an acceptance or declination of the assignment.
 5. Themethod of claim 2, wherein the temporary time frame is determined by thehost device.
 6. The method of claim 1, further comprising: upon thedetermining the ability of at least one of the host-designated remotemonitoring devices to react to an alert, revoking, by the secure server,assignment of the universal remote monitoring device, wherein therevoking includes removing access of the universal remote monitoringdevice to at least some of the data associated with the analyte state ofthe host.
 7. The method of claim 1, wherein the notification rules arewithin a scope of the set of permissions to the data associated with thehost-designated remote monitoring devices.
 8. The method of claim 1,wherein the data includes one or more of (i) retrospective sensor data,(ii) real time sensor data, or (iii) a trend in the rate of change ofthe analyte state of the host.
 9. The method of claim 1, wherein theanalyte state includes glucose level.
 10. A continuous analyte sensorsystem to implement the method of claim 1, comprising: a continuousanalyte sensor device worn by the host comprising the continuous analytesensor to detect signals associated with an analyte of the host, and asensor electronics module to perform at least some processing of thesignals to generate sensor data and transmitting the sensor data to thehost device; a non-transitory computer program product at leastpartially stored on the host device and including instructions that,when executed by a processor of the host device, causes the processor toperform at least some processing of the sensor data to produce the dataassociated with the analyte state of the host; and the secure server incommunication with the host device to perform the method of claim
 1. 11.A method for remote monitoring of health data, comprising: receiving, ata secure server, data associated with an analyte state of a host that isprovided by a host device operable to receive sensor data generated by acontinuous analyte sensor worn by the host, wherein one or more remotemonitoring devices are authorized by the secure server to accesspermissible data of the received data stored on the secure server basedon a set of permissions pre-selected and modifiable by the host for eachof the one or more remote monitoring devices, wherein the one or moreremote monitoring devices are assigned notification rules that definecircumstances to send a message to a respective remote monitoring deviceinformative of an event associated with the analyte state of the host;processing, by the secure server, an alert informative of a dangerousevent associated with the analyte state of the host, wherein theprocessed alert is within a set of notification rules associated with atleast one of the one or more remote monitoring devices such that thesecure server determines that the at least one of the one or more remotemonitoring devices should be sent a message associated with the alert;determining, by the secure server, that the message is duplicative as tothe at least one of the one or more remote monitoring devices based ondetermining that the at least one of the one or more remote monitoringdevices is located within a predetermined area where the host device islocated; and suppressing, by the secure server, the sending of themessage to the at least one of the one or more remote monitoring devicesbased on determining that the message is duplicative as to the at leastone of the one or more remote monitoring devices.
 12. The method ofclaim 11, wherein the dangerous event includes the analyte state of thehost exceeding a predetermined analyte concentration threshold or apredetermined rate of concentration change threshold.
 13. The method ofclaim 11, wherein the processing the alert includes receiving alert datafrom the host device, wherein the alert data is generated at one or bothof the host device or a sensor electronics device in communication withthe continuous analyte sensor.
 14. The method of claim 12, wherein theprocessing the alert includes generating, by the secure server, thealert by processing the data to determine if the analyte state exceedsthe predetermined analyte concentration threshold or the predeterminedrate of concentration change threshold.
 15. The method of claim 11,wherein the suppressing comprises suppressing the sending of the messageto the at least one of the one or more remote monitoring for apredetermined period of time, the method further comprising: sending themessage associated with the alert to the at least one of the one or moreremote monitoring devices after the predetermined period of time. 16.The method of claim 12, further comprising: prior to the suppressing,processing the data to determine if the analyte state exceeds a secondpredetermined analyte concentration threshold lower than thepredetermined analyte concentration threshold or a second predeterminedrate of concentration change threshold lower than the predetermined rateof concentration change threshold, wherein, if the analyte state exceedsthe second predetermined analyte concentration threshold or the secondpredetermined rate of concentration change threshold, sending themessage associated with the alert to the at least one of the one or moreremote monitoring devices after a predetermined delay, wherein thesending includes overriding the suppressing.
 17. The method of claim 11,wherein the permissible data includes (i) retrospective sensor data,(ii) real time sensor data, and (iii) a trend in the rate of change ofthe analyte state of the host.
 18. The method of claim 11, wherein theanalyte state includes glucose level.
 19. A continuous analyte sensorsystem to implement the method of claim 11, comprising: a continuousanalyte sensor device worn by the host comprising the continuous analytesensor to detect signals associated with an analyte of the host, and asensor electronics module to perform at least some processing of thesignals to generate sensor data and transmitting the sensor data to thehost device; a non-transitory computer program product at leastpartially stored on the host device and including instructions that,when executed by a processor of the host device, causes the processor toperform at least some processing of the sensor data to produce the dataassociated with the analyte state of the host; and the secure server incommunication with the host device to perform the method of claim 11.20. The method of claim 11, wherein the notification rules aremodifiable by the authorized remote monitoring devices within a scope ofthe set of permissions to the data associated with the respective remotemonitoring device.